You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After we upgraded to {N} 8.2.2 we found that during build, the CLI sets the targetSdk to 31 instead of respecting the value in App_Resources/Android/src/main/AndroidManifest.xml which was in our case set to 30.
The merged, final manifest in the APK has targetSdk 31
This is read from platforms/android/gradle.properties, defined as NS_DEFAULT_COMPILE_SDK_VERSION=31, applied in the platforms/android/app/build.gradle file through
def computeTargetSdkVersion = { -> project.hasProperty("targetSdk") ? targetSdk : NS_DEFAULT_COMPILE_SDK_VERSION as int }
Workaround: specify targetSdk in the config/android/resources/gradle.properties, e.g.
targetSdk = 30
Reproduction
in App_Resources/Android/src/main/AndroidManifest.xml set
check platforms/android/app/build/intermediates/manifest_merge_blame_file/debug/manifest-merger-blame-debug-report.txt or check the generated APK and it's embedded AndroidManifest.
Issue Description
After we upgraded to {N} 8.2.2 we found that during build, the CLI sets the
targetSdk
to 31 instead of respecting the value inApp_Resources/Android/src/main/AndroidManifest.xml
which was in our case set to 30.The merged, final manifest in the APK has
targetSdk
31This is read from
platforms/android/gradle.properties
, defined asNS_DEFAULT_COMPILE_SDK_VERSION=31
, applied in theplatforms/android/app/build.gradle
file throughWorkaround: specify
targetSdk
in theconfig/android/resources/gradle.properties
, e.g.Reproduction
in
App_Resources/Android/src/main/AndroidManifest.xml
setrun
ns build android
check
platforms/android/app/build/intermediates/manifest_merge_blame_file/debug/manifest-merger-blame-debug-report.txt
or check the generated APK and it's embedded AndroidManifest.Relevant log output (if applicable)
Environment
No response
Please accept these terms
The text was updated successfully, but these errors were encountered: