This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal.
I am trying to publish two APKs for the phone and tablet using the same package name, etc. How is this done with the Kony Viz build artifacts? Do I need to segment my project settings for Native Android and build twice?
If you publish your app to Google Play, you should build and upload an Android App Bundle. When you do so, Google Play automatically generates and serves optimized APKs for each user’s device configuration, so they download only the code and resources they need to run your app. Publishing multiple APKs is useful if you are not publishing to Google Play, but you must build, sign, and manage each APK yourself.
Excellent! That worked, however, I had to "Refresh" and "Save" the project to get KV to recognize it. That should be put in the documentation at the point where the doc instructs the Developer to add the file to the project folder structure.
I did the build and I see the ".aab" file in the dist/.../bundle folder. My next question is, am I supposed to build for both phone and tablet and upload both .aab files to Google Play? if not, how are the different packagings distinguished by Play? Keep in mind there are some forms, skins and controller code that are modified between the two device-type-builds.
When I build for Universal, I am getting some "DEX Merging" issues. According to some discussions I found, I have to resolve some inter-dependencies of library versions before it will merge correctly. I was able to successfully build for an Android Tablet and install it on my test device. I hope to resolve this issue soon and report back.
I am not able to de-compile the "dex jar" files to determine root cause of my build issue. Do you have a solution? Note: there are over 200+ files numbered 0.jar ... 200.jar ... etc. in the build intermediates folder. I believe it could be resolved by the framework to uniquely include libraries that are common to "phone" and "tablet" (although I do not have any tools to prove this theory).