-
Notifications
You must be signed in to change notification settings - Fork 12
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
expo 49 migration #80
Comments
Hey! Having a look... |
Same issue with a bare react-native project (no expo) using RN 0.72.3
There was a suggestion in similar issue to manually include the maven repo via the following. Note path was adjusted for monorepo.
This made no difference. |
Was able to get a build working by setting the local repository under
|
@divanc Hello, anything new about this? |
I was able to solve it via app.json. Add under plugins
If you are in a monorepo, then use |
I encountered the same problem with I encountered another problem after this. Expo somehow screws up the namespace in the build.gradle file, so the local development build will fail. The problem exists in both SDK48 and SDK49. The solution is to correct the namespace manually. I mention this here because I figure many are upgrading their Expo SDK because Google is enforcing targeted API Level 33 in a few days. |
Thank you @megacherry and @jasonpeinko |
Ouch, sorry guys, missed that... Strange that Expo is able to find one lib and fails to find another |
This solved my issue. |
Hi folks, I'm migrating from expo 48 to 49 ... and the gradle version is being migrated to version 8.
And react-native-adapty is throwing an error:
Can I have some help?
Thank you!
Originally posted by @rafakwolf in #79
The text was updated successfully, but these errors were encountered: