You can upload 4 separate builds to Google Play for each the archs and when the user installs only the apk for the user's device arch will download. This alleviates having one huge apk. Some devices have apk size limits that you can hit. The only hitch is that the build number bust be different for each. I am working on a IDE build plug-in that will build all 4 to separate apks and automatically up the version number by 1 for each arch. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net
-----Original Message----- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Monte Goulding via use-livecode Sent: Thursday, May 02, 2019 6:39 PM To: How to use LiveCode Cc: Monte Goulding Subject: Re: Android needs 64 bit builds > On 3 May 2019, at 4:07 am, J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Wow. X86 too! Now we can use the faster emulator. :) Yes that was the main reason for us doing x86 and x86_64 although there are some devices available for those architectures they aren’t very common so you probably only want to build for arm7 and arm64 when releasing to avoid bloating your app too much. To make things simpler the Test button for android will detect the architecture of the target device/emulator and build just for that even if you don’t currently have it selected in the standalone builder. Cheers Monte _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
