@vlads and @Rob, I had just removed my 5 plugins, and the app will start-up. So, now I’m going to work one-by-one to figure out which one causes the app not to load and start.
Can you tell me which one you already know will not work yet?
@vlads and @Rob, apparently, the Kochava plugin is the culprit. I see that it is a CoronaLabs plugin, but I’m still going to reach out to my contact there and let them know of the problem and to make sure to be available should you need their help.
After you get the Kochava plugin working for 64-bit, I can then do some comprehensive testing of the 64-bit version for 2 of our 3 apps - I mean hours and hours and hours. Our 3rd app requires numerous other plugins, which will be a lower priority to fix. Thanks to everyone who is working on this, both within CoronaLabs and the community here, to get us all up and running again in 64-bit for Android before the deadline.
not have character in path
i run this in terminal but not work.
now, I build in mac by corona sdk version 3498. It’s work!!
but i upload .apk file to play store. It’s not work.
Because the file’s large size.
Unoptimised APK
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.
Resolution:
Use the Android App Bundle to automatically optimise for device configurations, or manage it yourself with multiple APKs.
@troylyndon please leave the “Corona:v *:s” off of the adb logcat. When you use “Corona:v *:s” you’re filtering out only the Corona activity. You’re missing messages from the Kochava library, Google Play and other libraries. Your adb logcat will be filled with a bunch of useless messages not related to this, but as of now, you need to dig through the output looking for non-Corona errors.
Without that we have no idea what’s going on.
@fairy.sa, You will continue to get that warning as long as you are uploading .apk files to Google Play. Part of Android-64 bit is the ability to use .aab files instead of .apk files. These .aab files allow Google Play to optimize the download. The .aab file is created along side the .apk file, just upload it instead of the .apk.
Now you will have to opt-in to Google App Signing, but it was pretty easy and you may have to update your keystore to a more modern format, but Google Play walks you through that when you upload the .aab file
[member=‘fairy.sa’], if you notice, modern builds produce two files - one apk, another aab. AAB stands for A ndroid A pp B undle. You can try submitting it.
Also, note, this is all in early alpha. Make sure to test your apps!
I have several pure Lua plugins that I’ve been meaning to add to the marketplace, but they’ve been delayed due to important client projects of mine. Does this 64-bit build affect pure Lua plugins at all or is the documentation concerning them still up to date?
plugin.OneSignal: Error: contain native library for armeabi-v7a but not for arm64.
plugin.amplitude: ERROR: Self-Hosted plugins was not activated.
plugin.adjust: ERROR: Self-Hosted plugins was not activated.