-
Notifications
You must be signed in to change notification settings - Fork 322
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 support is down #473
Comments
I think the easiest solution for now is to use I’m not familiar with Expo, but from some SO discussion, it seems that you still need to modify Even if you have changed this, this might still not work because it still depends on whether the build server have installed the required toolchain for android sdk 31. |
Call out to the expert! @EvanBacon hi, do you know whether EAS build supports Some native breaking change forced the app to be compiled with android sdk 31 to support Android 12: Thanks! |
Thanks, @whitedogg13. With that version, the android app worked here. I'll keep following this thread and keep searching for solutions on the Expo side. Cheers! |
I'm also getting the same issue using expo, if I find a solution I'll post it here |
It may not be ideal, but running |
@IsTheJack |
making "minSdkVersion": 31 seems to work but this time firebase crashlytics fires an error while building. Is there any way to arrange different "minSdkVersion"s for different packages? |
To fix that on Expo apps. Get the last version of {
"expo": {
...
"plugins": [
[
"expo-build-properties",
{
"android": {
"compileSdkVersion": 31
}
}
]
]
}
} |
Edit: The final solution for me #473 (comment)
Versions:
That issue is related to #469, but maybe it have a different solution
I'm getting this error on EAS Build:
I tried to solve that adding
"minSdkVersion": 31
to"react-native-nfc-manager"
plugin config onapp.json
:But I keep getting the same error.
The text was updated successfully, but these errors were encountered: