Are you using split ABIs or one big APK with all arches (for gradle: yes
) ?
I’m usinng product flavours.
productFlavors {
/* doesn't work when they all work individually ... because of the two different NativeFlite.java
fat {
dimension "abi"
ndk {
abiFilters "x86", "armeabi-v7a","arm64-v8a"
versionCode = 0;
}
}*/
armv7a {
dimension "abi"
ndk {
abiFilter "armeabi-v7a"
versionCode = 100 + android.defaultConfig.versionCode;
}
}
x86 {
dimension "abi"
ndk {
abiFilter "x86"
versionCode = 300 + android.defaultConfig.versionCode;
}
}
arm64 {
dimension "abi"
ndk {
abiFilter "arm64-v8a"
versionCode = 200 + android.defaultConfig.versionCode;
}
}
}
I don’t use splits. Because normally I have even more versions ( pre android kit kat and afterwards) which don’t work with splits if I remember well
Yes, so instead of yes
put fat
or whatever the flavor name is.
gradle:
- fat
…and maybe the resulting APK is detected…if it’s not, you can still use:
output: path/to/nameofresulting.apk
or name*.apk
etc
it kind of works if I put
-armv7a
I have an apk with “armeabi-v7a” and “x86” (why ?) libs inside
If I put
-armv7a
-x86
it says “Task ‘assembleArmv7aX86Release’ not found in root project ‘flitewrapper’. Some candidates are: ‘assembleArmv7aRelease’.”
Don’t list multiple.
It doesn’t work if you put fat
?
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.