Android 64-bit is here…

23 July 2019

Android 64-bit is here…

Whew! That was a challenging update… But our engineering team has been working very hard and with much fanfare, we would like to introduce to you a publicly available Android 64-bit build of Corona.

If you check the daily builds, you will find a new daily build: 2019.3504. This build should be stable enough for a public beta and for you to release apps to Google Play that meets all of their current new requirements.

This includes:

• The August 1 deadline for 64-bit support for new apps (updated apps have a year to implement).
• The August 1 deadline to support Android SDK 28/Android 9/Pie (updated apps have to be using them by November 1, 2019)
• The recently changed AdMob requirements that require the AppId be included in the AndroidManifest.xml (build.settings file.)
• All Corona controlled plugins, updated to 64-bit, and many have been updated to the most recent SDK for those app plugins.
• Support for Android responsive icons
• Faster builds that are less dependent on network connections.
• Support for Android App Bundles (.aab files)

While we are certain that there may still be edge-cases that need addressed, the only way to find them is to open this up to a wider audience. If you run into any edge case, please start a new thread in our Community Forums Android 64-bit testing channel (please don’t add it to an existing thread.)

There are a few things to be aware of.

• .aab files require you to use Google’s new App Signing procedure. While we have discouraged this in the past over your standard keystores, you have to use this now and once you convert your app to use Google’s new App Signing, you have to use it going forward, but the gains by having your app size reduced is worth it.
• Your first Android 64-bit build may take some time as we need to download additional content (about 250 Mb total) to support the more local-natured building. Future builds should run noticeably faster.
• Android’s new responsive icons require a completely different file/folder structure than putting a few Icon-*dpi.png files alongside main.lua. The best thing you can do is to use the Corona “Welcome” window, create a new project and copy the AndroidResources folder to your project. Look at how the files in each of the various folders are named and sized, and create your new app icons using those names and sizes and overwrite our template icons. We are working on the guide explaining the topic.
• If you’re using AdMob or Appodeal, you must add some new content to your build.settings. See yesterday’s post for details.
• If you’re still using the legacy AdMob plugin [plugin.google.play.services], you must remove it.
  Several plugins still doesn’t have full 64-bit support.

It is recommended that anyone building for Google Play, using ad or other plugins, update to this build as soon as possible.

Remember to report issues regarding this update to the Forums!