Closed jmcmullen closed 1 year ago
we’re using reanimated 3 now, so you need to build the expo dev client instead of expo go. you can ignore those expo warnings if you do that
Fixed in the latest starter. If you run the script again, it'll work as long as you use an Expo Dev Client. Thanks!
I had the same problem, may be useful to add this information to the readme. I tried to use the expo dev client and found these steps that I followed:
But then my build fails with this error:
[Reanimated] Unable to resolve react-native location in node_modules. You should project extension property (in app/build.gradle) REACT_NATIVE_NODE_MODULES_DIR
with path to react-native.
Is there maybe a guide how to go about this?
does ios work? i only tested ios
you should run eas commands in apps/expo, not in the solito root
After trying around for a bit, I got it to work following your instructions in the release notes: https://github.com/nandorojo/solito/releases/tag/v3.1.1 and by changing the gradle distributionUrl in apps\expo\android\gradle\wrapper\gradle-wrapper.properties to distributionUrl=https\://services.gradle.org/distributions/gradle-7.4.1-all.zip
I've just created a new project from the tailwind starter template and I get the following error:
If I run the suggested
npx expo install react-native@0.71.4 react-native-reanimated@~2.14.4
command fromapps/expo
, expo go crashes as soon as I attempt to open the app inside the simulator for iOS.Really keen to give Solito a go, any ideas what could be causing this?