Closed HeRo002 closed 1 year ago
There seems to be a limited workaround for creating AAB files by Robert Flatt:
Buildozer does not currently build .aab files. The following is a summary of a workaround posted on Google Groups - https://groups.google.com/g/kivy-users/c/LmoegwYuEEk/m/II-wuO-nAgAJ . This workaround only applies to single architecture bundles, there is no workaround for multi architecture bundles. [Because architecture specific Kivy app code is in the apk in assets/private.mp3, but in .aab assets are architecture independent. A resolution would require renaming private.mp3 for each archicture, and the app picking the right one for the device.]
But I haven't tried it myself yet.
Hello! The creation of aab
files have been added via: https://github.com/kivy/python-for-android/pull/2467
Have you managed to find a solution to the This APK contains native code
warning? I'm facing the same warning. Except for me it's This App Bundle contains native code
, the rest is the same.
No. I haven't really worked on it. My project has been kind of 'sleeping' for some time. :-)
Hello! Has any of you solved these warnings? I get the same warnings too: 2 MESSAGES FOR VERSION CODE 10211 Warning There is no deobfuscation file associated with this App Bundle. If you use obfuscated code (R8/proguard), uploading a deobfuscation file will make crashes and ANRs easier to analyze and debug. Using R8/proguard can help reduce app size. Learn More
Warning This App Bundle contains native code, and you've not uploaded debug symbols. We recommend you upload a symbol file to make your crashes and ANRs easier to analyze and debug. Learn More
I was using https://gist.github.com/Guhan-SenSam/35c5ed7da254a7c0141e6a8b6101eb33 to generated the .AAB file
Hello, @yayazhao! No, I didn't solve the warnings. But I made a little bit of a research, and contacted Guhan-SenSam
, the guy who wrote the gist you were making .aab
from. He had uploaded Kivy application recently back then. And from his experience, these warnings didn't make any difference on the logs that Google Play
provides you, they were without any obfuscation, and you could read the logs easily.
My research showed that this was due to p4a stripping the debug symbols of compiled .so
files. You can upload debug symbols in Google Play Console
separately from your .aab
file, in a form of just .so
files with the debug symbols. I have tried many things to get it not strip the debug symbols from these files. It seemed to work, if it would not be a release compilation (no --release
flag in p4a, or a buildozer debug ...
in buildozer) and including --with-debug-symbols
(no idea how to do this with buildozer, p4a only I guess)
Then after compiling that apk, you can unzip it, and collect all of the needed compiled files with debug symbols.
I have not uploaded these files though, so this is not 100% tested. You can get the debug symbols, this is tested. Can you get rid of this warning? Well, it needs testing.
To sum everything up:
Google Play
with no problems.--with-debug-symbols
(you will probably need to do this in p4a, no idea how to do this in buildozer).so
files.Google Play Console
Hope you will be able to get rid of these warnings!
Thanks for all the information, @AndyRusso , I will look more based on this. Have a great holiday!
👋 @HeRo002, we use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please use our support channels to get help with the project. Let us know if this comment was made in error, and we'll be happy to reopen the issue.
Hi!
I have successfully compiled 2 signed APK release files (32bit and 64bit). When I upload them on the Google Play Console, I get these 3 warnings:
3 MESSAGES FOR VERSION CODE 8213 Warning This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimising your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower installation success rates and take up storage on users' devices.
Warning This APK contains Java/Kotlin code, which might be obfuscated. We recommend that you upload a deobfuscation file to make your crashes and ANRs easier to analyse and debug. Learn more - https://developer.android.com/studio/build/shrink-code#decode-stack-trace
Warning This APK contains native code, and you've not uploaded debug symbols. We recommend that you upload a symbol file to make your crashes and ANRs easier to analyse and debug. Learn more - https://developer.android.com/studio/build/shrink-code#native-crash-support
On https://groups.google.com/g/kivy-users/c/8AjU7H8Cpic/m/3KwFhcnWBAAJ there is a discussion that warns that Buildozer will seize to function in August 2021, because Google will start to enforce mandatory use of the app bundle format...
So I hope someone will be able to solve these issues before that. Thank you. :-)
PS: I had to specify "android.api = 29" in buildozer.spec.
Versions
Description
// REPLACE ME: What are you trying to get done, what has happened, what went wrong, and what did you expect?
buildozer.spec
Command:
Spec file: