-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When uploading APK release files to Google Play: 3 warnings per file #1290
Comments
There seems to be a limited workaround for creating AAB files by Robert Flatt:
But I haven't tried it myself yet. |
Hello! The creation of Have you managed to find a solution to the |
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: Warning 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 My research showed that this was due to p4a stripping the debug symbols of compiled 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:
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. |
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:
The text was updated successfully, but these errors were encountered: