Thank you for replying! I am thinking that the following bit might apply
Avoid importing the
expo package in bare apps
Using the approaches above, you should avoid importing the
expo package in bare environments. If you import anything from the
expo package it will run code that assumes you are within the client runtime environment and throw an error.
This is relevant when I run
yarn ios and probably why I get the following error in the simulator after that:
The Expo SDK requires Expo to run. It appears the native Expo modules are unavailable and this code is not running on Expo.
Unfortunately the docs are not that informative nor suggest a solution or actions to take.
In any case I would like to know how I can build my container app to include the Action Extension when I eject.
I assume the build information for the main app (generated by Expo) are in its Info.plist file and turtle-cli builds the app using those information. If that’s the case maybe it can build the Action Extension as well?