Android - Different Builds

[JJS]

as far as i've read, Google Play will look for the architecture of the 
device where the app will be installed and then pushes the best fit to it.

Just like LC950dp1 now is checking the device before pushing a stack to 
test on your phone. Monte confirmed LC does it and you can also quickly 
see a popup telling his.


I guess the build-in emulator makes the app work slower then using a 
build for the architecture


Regards,

Jerry(Sphere)

Op 13-6-2019 om 20:28 schreef Ralph DiMola via use-livecode:
> This thing that confuses me is that the error was for "shadowing". My question is why does armv7 shadow(ie; target the same device natively) as arm64?
> I wonder if there should be only 2 builds 1)armv7 AND arm64 2) Intel AND Intel 64? Theoretically the armv7 and arm64 will both work on a arm64 device. Also Intel and Intel 64 build would work on an Intel 64 bit processor. But this logic breaks as an armv7 build will work on an Intel device(via built-in emulator)???
>
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdimola at evergreeninfo.net
>
> -----Original Message-----
> From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of JJS via use-livecode
> Sent: Thursday, June 13, 2019 2:10 PM
> To: Sannyasin Brahmanathaswami via use-livecode
> Cc: JJS
> Subject: Re: Android - Different Builds
>
> your version code needs to be higher than the previous one, each time you upload an update
>
> you could do:
>
> arm-v7a vc1      arm64 vc2         x86  vc3           x86-64 vc4
>
> then next update of your app:
>
> arm-v7a vc5      arm64 vc6         x86  vc7           x86-64 vc8
>
> etcetera
>
> when you manage a release, then you can upload 4 apk's to the console for that release
>
> But whatever version code you now have, the next ones need to be higher every time.
>
> As far as i understand you need to upload all apk's per release and not a release per apk architecture
>
>
> Op 13-6-2019 om 15:08 schreef Sannyasin Brahmanathaswami via use-livecode:
>> But what about this one, it is an "error," not a "warning
>>
>> For  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.
>> ------------
>>
>> But the other three are all different
>> X86
>> X86_64
>> Armv7
>>
>> So what about the error? It saying "will not be served to any users" that's cause to be concerned.
>>
>> Do I need to set up a separate release for this one arm64-v8a?
>>
>> BR
>>
>>
>> On 6/13/19, 12:21 AM, "use-livecode on behalf of JJS via use-livecode" <use-livecode-bounces at lists.runrev.com on behalf of use-livecode at lists.runrev.com> wrote:
>>
>>       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
>>       
>>       
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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