-
Notifications
You must be signed in to change notification settings - Fork 667
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
The Android app gets stuck on startup. #5491
Comments
Can you add renpytom@gmail.com to the testers for your app, and sent me your apps name? I'd like to see what errors I get. |
Hi Tom, |
Extracting the APK won't work - it needs the additonal files that are included in the .aab to work. You need to use bundletool to install it. Ren'Py does that for you. |
Aside from the tests done with Android Studio, have you tried downloading the App from Google Play and running it on an Android device? |
Just for information, bundletool with the mode=universal option generates a .APKS file which is renamed with a .ZIP extension and once uncompressed two files emerge:
toc.pb file is not directly needed to run the APK extracted from the .aab file using bundletool with the --mode=universal option. Here's why: Universal APK: The --mode=universal option in bundletool creates a single APK that includes all the resources and code needed for the app to run on any device configuration supported by the app. This eliminates the need for the app store to split the app based on device specifics. toc.pb for Splitting: The toc.pb file is primarily used when dealing with app bundles containing multiple split APKs. These splits target specific device configurations (like screen size or architecture) to reduce app size. Universal APK is Self-Contained: Since the universal APK already contains everything, it doesn't need the toc.pb file to understand its own structure. It has all the necessary resources and code within itself to function. In conclusion, I believe that running universal.apk from Android Studio is the same as downloading the APK from Google Play and running it on an Android device and in fact the behavior is the same, the app crashes as soon as it starts. |
Does it fail when you use Ren'Py to install the game on a device? |
No, I don't use Ren'Py for installation. |
Hi Tom, |
Hi Tom, |
You need to use Ren'Py to install the AAB, downloading it yourself won't work. People have gotten it working in Google Play, but Google Play has had bugs as well. |
I produce the AAB with Renpy and upload it to Google Play. |
That should work. You do need to uninstall the game from your device and reinstall it from google play to have it work. |
I tried but nothing changes.
|
I built an android app with Renpy and uploaded it to Google Play (.aab file).
Google play console gives me this error:
""This item may not have a label readable by screen readers".
Same error if I load the build of a new VN without modifying it.
I tried downloading the app from Google Play on my phone. When start it remains stuck displaying the presplash file.
The apk file generated by Renpy however works well on my phone.
I extracted the apk from the .aab file with Bundletool and tried to run it with the Android Studio emulator and it crashes like on the phone.
I think at this point there is a problem with how Renpy creates the .aab file.
Amazon instead asks for the APK file and therefore there are no problems: https://www.amazon.com/gp/product/B0D2Y77WP1
I am using:
Renpy 8.2.1.24030407
jdk-21.0.2+13
I attach some screenshots and ask what other information can be used to understand what the problem is.
Thank you
The text was updated successfully, but these errors were encountered: