Our project has split abi builds. Recently we included 'arm64-v8a' to the list of ABIs as recently required by Google Play and now the plugin uploads the arm64-build instead of the one we have been uploading before armeabi-v7a and our testers are unable to install our app due to incorrect ABI.
If it helps, this is where the arm64-binary has this path when built through the plugin:
./app/build/outputs/apk/flavorName/release/app-flavor-name-arm64-v8a-release.apk
while the arm7-binary has this path:
./app/build/outputs/apk/flavorName/release/app-flavor-name-armeabi-v7a-release.apk
android {...
splits {
abi {
enable true
reset()
include 'armeabi-v7a', 'arm64-v8a', 'x86', 'x86_64'
universalApk false
}
}
...}
Our project has split abi builds. Recently we included
'arm64-v8a'
to the list of ABIs as recently required by Google Play and now the plugin uploads the arm64-build instead of the one we have been uploading beforearmeabi-v7a
and our testers are unable to install our app due to incorrect ABI.If it helps, this is where the arm64-binary has this path when built through the plugin:
./app/build/outputs/apk/flavorName/release/app-flavor-name-arm64-v8a-release.apk
while the arm7-binary has this path:./app/build/outputs/apk/flavorName/release/app-flavor-name-armeabi-v7a-release.apk