-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run expo app after installing react-native-executorch #74
Comments
Hello, is your app running on new architecture? If yes, you can try to open .xcworkspace of your app in xcode and try to clean build folder(Product -> Clean Build Folder). Also running app from xcode can provide more understandable errors. |
hi @NorbertKlockiewicz Yes it's new arch, i just tried cleaning build folder and running from xcode with no different result unfortunately, also i tried the example project and that worked so i know it's not my machine but most likely my project. ![]() |
I've investigated this issue and as you are using firebase you have for sure set |
Thanks so much for looking into it and i'll be sure to keep an eye on future releases! |
I'm also facing this issue @NorbertKlockiewicz - the issue is that upcoming releases are lock to the new architecture. |
@al3xstathis add a pre_install block into your Podfile if you're using
|
Description
Expo run phase fails for same errors after multiple remove node_modules, pod install. Behaviour is the same when target is simulator or real device. After i removed the package and re-ran everything went back to normal.
alexstathis@MacBook-Pro memory-journal-app % expo run:ios
env: load .env
env: export EXPO_PUBLIC_API_URL
✔ Installed CocoaPods
› Skipping dev server
› Planning build
package.json
Steps to reproduce
This is the full output of my installation process
Snack or a link to a repository
React Native Executorch version
0.2.0
React Native version
0.76.5
Platforms
iOS
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
No response
AI model
No response
Performance logs
No response
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: