Closed aleferna12 closed 11 months ago
Here is another way https://github.com/Android-for-Python/Android-for-Python-Users#release-builds It is still in development, if you have any questions, ask on Discord. https://discord.gg/UJ3PGbhs
👋 @aleferna12, 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.
Versions
Description
Hey, I'm not sure this is the right place to place the issue but it is my best guess. Due to Google's new publishing policy, 64 bits architectures are now required to publish apps on the Play Store. However, I've encountered a weird error in trying to compile my app using the arm64-v8a ABI.
While buildozer successfully creates a working arm64 APK, it has no native tools for the packaging of AABs, another new requirement from Google. To create an AAB, required gradle and android gradle plugin distributions are 6.5 and 4.1 respectivelly. Because both default distributions from buildozer are bellow these versions (and as far as I know there is no way of manually determining which version of gradle tools to use), the only way I found to build the App Bundle was to import the generated android project (found in "./.buildozer/android/platform/build-arm64-v8a/dists/myapp__arm64-v8a") to Android Studio, update gradle and gradle plugin to the referred versions and use the "Generate Signed App Bundle" function. This works correctly in generating the AAB. However, after uploading the file to the Play Store and installing it on my phone, it will always crash on start due to a
SDL : nativeRunMain(): Couldn't load library /data/app/~~IgYazZl-zq9Ksnnzir_hlQ==/com.example.myapp-UoApMu0RyRwPdP0Tk8P5tA==/lib/arm64/libmain.so
error. Inspecting the AAB shows that the libs were correctly extracted:I've searched the internet for solutions and have tried everything I could think of. There are many reports of a similar issue coming from Unity users, but none of the suggestions worked for me and the general solution seems to be downgrading Unity and recompiling, which of course isn't of any help in my case. Any help is appreciated.
buildozer.spec
Command:
Spec file:
Logs: logcat.txt