breautek commented on issue #1643: URL: https://github.com/apache/cordova-android/issues/1643#issuecomment-1681513924
Sorry for the misunderstanding. They do still exist, as you can see [here](https://github.com/apache/cordova-android/blob/master/templates/project/app/build.gradle#L208) and [here](https://github.com/apache/cordova-android/blob/master/templates/project/app/build.gradle#L87) (among other places in the gradle script). But what I'm saying is what primary used by third-party tools that supplied native shared libraries that was architecture specific, and those tools aren't around anymore so I don't think these are used very often and they aren't really maintained or tested. Additionally using mulltiple APKs today is obsolete, even if you have shared libraries embedded that are architecture specific. That's because the android app bundles provides a way to create a device-specific APK on the fly so each device can get the most optimized version of the APK as possible. Cordova by default will produce an APK when building a debug version, since it assumes you're going to deploy to a local device or emulator. By default it will produce an AAB (Android App Bundle) file when building with `--release` flag as Google Play expects bundle files, not APKs. I do not know if `cdvBuildMultipleApks` actually works or not, but bundles should replace the need to manage multiple APKs manually. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
