I have encountered several severe problems on Android standalone build after moving to SDK 33 up to the point it’s unusable and forces me to downgrade.
This includes issues with camera, barcode scanner (still investigating) and Segment analytics. I’ve also encountered problems with animated-switch-navigator (depends on react-native-reanimated and works fine on iOS but breaks on android) and some minor bugs as well.
This is strange given that iOS standalone build and Android expo application can handle all this just fine. Seems like the problem is with standalone build process on android rather on SDK 33 itself.
So the point is - will this problem be addressed in near future, before SDK 34 release? Does it solvable without detaching and if so - how?
Could you elaborate on what the issues are? If you do think you’ve found a bug, please file an issue on our Github (providing all the info we ask for- especially a repro!)
This could be the result of you building your binary while we temporarily had custom builds enabled and thus the unimodules package was not installed as it would normally be. Could you try updating your expo-cli version if it isn’t already updated and then building a new binary?
Thanks, I can confirm that later this week one of the android standalone build just fixed issues for us - all of missing native modules just appear back (well, at least segment and camera for sure) where they should be. We did however recreated application with new bundle id and install it through google play this time - it may or may be related to fixing an issue.
Hey, does anyone know about the error “cannot find symbol method getCameraId()” while building the application? You guys are discussing after build problems. I cannot even build the app in android studio after upgrading to SDK 33.
PS: I’m using expokit. Platform: Android