Harry
That's a nice suggestion. I have been using react myself - could contribute to it too;
upgraded to expo-47 from 45 - the warning still is there; haven't tried above code though.
@dannyhw - thanks for quick action on this; have updated the info btw. Also, a nice tool, no doubt - 6-alpha is coming along nicely too. Cheers to that too.
@dannyhw - currently this is in a project that I'm working on; I'll try to reproduce it in a sandbox and share here.
Any updates here? And also, @KPIshnik , @AnnaVl92, @Nandansv and @freja49 - did you guyz face any errors or operational issue while working with the library except the warning.
what happened to this issue? And I'm wondering why there is no `@nx/ignite` at par with `@nx/expo` and `@nx/react-native`? @flexbox - kudos to awesomely compiled response above; I'm curious, did...
@flexbox thanks for answering. And agreeable reasoning. :) App is for a fintech product in crypto space. The plumbing that I was engaged up till like yesternight here has come...
The latest of the alternative mentioned above doesn't support the new architecture.
Running ok while trying using the latest expo and latest package - ` "@react-native-menu/menu": "^1.2.0", "expo": "~52.0.24", ` - Successfully created dev-build using eas build ios(locally) and android(eas-servers) - Successfully...
Hi @Overtorment. Thanks for indulging. 1. It is absolutely possible to build the app locally using `eas build --locally`. More [here](https://docs.expo.dev/build-reference/local-builds/). 2. The native code can-be generated on fly while...