Reputation: 19283
I recently noticed that the gradle settings had the following configurations:
android {
buildToolsVersion = 30.0.2
defaultConfig {
minSDk = 33
targetSDK = 33
}
}
As noted, buildToolsVersion is not matching the targetSDK. But during tests and publications of the last months nothing bad has happened.
Now, I haven't modified anything related to gradle or sdk recently, however in the recent app upgrade publication (September 2023) app started to crash for some architectures when they tried to load native libs.
Could it be possible that incompatible buildToolsVersion affect how Google deliver bundle based apks or how libs are compiled and built?
The build version wasn't updated on error and now I am up to using 33.0.2 which should be the match for sdk 33.
Upvotes: 0
Views: 202
Reputation: 30652
As long as you're using Android Gradle Plugin 3.0.0 or later, it will automatically pick the correct version to use. (You should only need to specify it explicitly if there's a problem with the default version)
See SDK Build Tools release notes
Upvotes: 0