Android - Different Builds

JJS jjs at krutt.org
Thu Jun 13 06:20:51 EDT 2019


4 separate builds give the same optimize warning which you can ignore.

There is a feature request done to have a swith in the standalone 
settings, so one can choose to have one big build or 4 separate builds 
(or to the nr of set architectures)

The playstore will push the correct build to the phone. So upload 4 
builds, each having a different increasing version code.


regards,

Jerry

Op 13-6-2019 om 04:57 schreef Sannyasin Brahmanathaswami via use-livecode:
> Hmm, I'm getting warnings
>
> First I built all 4,
>
> All four have different version codes.
>
> But for the arm64-v8a
>
> ERROR
> 1 message for APK 7
> Fully shadowed APK
>
> Problem:
> This APK will not be served to any users because it is completely shadowed by one or more APKs with higher version codes.
>
> Resolution:
> Remove this APK from your release or review the targeting and version codes of the APKs that you are including in this release.
> ----
> And for all four architecture, with different version codes we get the same warning
> 	
> Unoptimized 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 optimizing 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 install success rates and take up storage on users' devices.
>
> Resolution:
> Use the Android App Bundle to automatically optimize for device configurations, or manage it yourself with multiple APKs.
> Unoptimized APK
>
> # And one final warning on the  armeabi-v7a
>
> This release is not compliant with the Google Play 64-bit requirement
>
> The following APKs or App Bundles are available to 64-bit devices, but they only have 32-bit native code: 14.
>
>  From July 31, 2019 all releases must be compliant with the Google Play 64-bit requirement.
>
> Include 64-bit and 32-bit native code in your app. Use the Android App Bundle publishing format to automatically ensure that each device architecture receives only the native code it needs. This avoids increasing the overall size of your app. Learn More
>
>
>
> # I don't know what to do?
>
> Ralph wrote:
>       You can have multiple APKs in production(internal/alpha/beta for the matter) if 1) the version code is different 2) they target different architectures.
>      
>      
> On 6/12/19, 12:21 PM, "use-livecode on behalf of Sannyasin Brahmanathaswami via use-livecode" <use-livecode-bounces at lists.runrev.com on behalf of use-livecode at lists.runrev.com> wrote:
>
>      OK!
>      
>      That's what we need hear. Thanks  Ralph!
>      
>      
>      
>      On 6/12/19, 12:17 PM, "Ralph DiMola" <rdimola at evergreeninfo.net> wrote:
>      
>          You would be better off making 4 builds 1 for each architecture. This way instead of 1 huge apk you will have 4 smaller ones. Increment the "version code" for each of the 3 additional builds. Upload all 4 apks to the PlayStore. Making one large build has 2 bad side effects. 1) you might not target as many devices because of smaller apk size limits on some devices 2) the download/install will be slower.
>          
>          You can have multiple APKs in production(internal/alpha/beta for the matter) if 1) the version code is different 2) they target different architectures.
>      
>      _______________________________________________
>      use-livecode mailing list
>      use-livecode at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode




More information about the Use-livecode mailing list