To open a project structure, press Ctrl+Alt+Shift+S. This happened to me also on 31.0.0.rc5 release. It is possible to copy it from other versions, but it won’t work if you have your entire team do it and it fails on your server pipeline. My adle configuration was the same as above.īuild-tool 31.0.0 is missing DX at path-to-sdk\build-tools\31.0.0\dx.bat Android Studio will download BuildTool V30 automatically and modify project settings. TargetSdkVersion is now 31 to 30Ī lightbulb will appear on the modified lines. Go to Gradle Scripts -> adle File and check the Project code panel.Ĭhange 3 places: compileSdkVersion and buildToolsVersion. Android Studio will automatically download BuildTool Version 30 and modify project settings. A pghtbulb error will occur on modified pnes. Just go to Gradle Scripts -> adle file and change 3 places: compileSdkVersion and buildToolsVersion. You can remove the SDK manager error and install it again. I will have no clue if this can even build on 32 until I get there, as was stated goal was to build for 31 to be Nov 2022 compliant.To Solve Installed Build Tools version 31.0.0 is corrupted. By requiring 32, Stripe may very well be limiting what of the available libraries an app can use at all.īecause today the target is 30 or 31 depending if you are a new or old app. In many cases other dependencies of an app only NOW update to target, to comply with the NOV 2022 deadline. The app won't build using compileSdkVersion = 31 only compileSdkVersion = 30. Yes, and this is the issue with Stripe pre-targeting. In your example above, you have compileSdkVersion still set to 30, which will not work on the most recent version of Stripe React Native. Most stable apps are following the minimum target for full library and decency access. They roll forward in August and November of each year. It takes time for everything to be good and ready. Is the "current" ver of STRIPE intended to be beta, and we actually should be installing the last respectfully anything higher than Google mandated targets is "beta" they release and endlessly update. If it comes to it and other things are not 32 ready we use, what ver should be rolled back to for STRIPE to be 31 compliant? Wondering if that might fix the POD error. I opened a case on the "pod error" here seems at least one more person is having it. Is there a reason STRIPE is forcing beta usage? Ideally, you wait until they are not their number but their Android OS Ver: I belive 12L and 13. To be honest, I do not even have 32 or 33 installed, they go through so many revisions and they are "beta" targets right now. And unfortunately, I can not test that at the moment with all the dependencies to resolve. I did not test building Android with 32, only 31, before I started to migrate the old app onto this core. The current ver of this library won't pod install. But STRIPE it seems is a breaking change here. Smartphone (please complete the following information):īasically, our old app can not build using 31 so rebuilding on a new core. The app builds successfully when using the library with fresh RN projects.ĭesktop (please complete the following information): Is greater than this module's compileSdkVersion (android-30).ĭependency: androidx.activity:activity-compose:1.4.0.ĪAR metadata file: /Users/tom/.gradle/caches/transforms-3/6105d9693b6d1b89f331872365193f55/transformed/jetified-activity-compose-1.4.0/META-INF/com/android/build/gradle/aar-metadata.properties. Install the library via yarn add Run the android build via yarn run androidĮxecution failed for task ':app:checkDebugAarMetadata'.Ī failure occurred while executing .ĭependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties).Create a new React Native project via npx react-native init. The latest version of the library (0.2.4) appears to break the build process for RN Android projects due to requiring a higher minCompileSdk than is specified in standard React Native projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |