RE: Android - Different Builds
My understanding is if there is 1 large apk then the PlayStore will download the entire apk and the device makes the choice. If you have 4 separate apks then the PlayStore will download the best apk for the device. 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 JJS via use-livecode Sent: Saturday, June 15, 2019 9:55 AM To: J. Landman Gay via use-livecode Cc: JJS Subject: Re: Android - Different Builds That's a good question and to which i have no answer. Op 15-6-2019 om 17:45 schreef J. Landman Gay via use-livecode: > Is a combined LC app the same as the bumdle the Play Store expects? I > think the Play Store extracts and sends only the parts the user needs. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software > | http://www.hyperactivesw.com On June 15, 2019 2:37:40 AM JJS via > use-livecode wrote: > >> you can choose yourself. >> >> You can submit a bundle (1 big apk) with different builds, or you can >> upload different builds per release >> >> >> i have opted out on Google's signing, because i don't what happens if >> you use their app shrinking method >> >> >> Op 15-6-2019 om 05:51 schreef J. Landman Gay via use-livecode: >>> For testing we could just do what we do now, since you can >>> distribute to testers privately. I think we'd only need the bundle >>> when submitting to the Play Store. >>> -- >>> Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive >>> Software | http://www.hyperactivesw.com On June 14, 2019 10:01:40 PM >>> Brian Milby via use-livecode wrote: >>> >>>> From reading a little about it, I’m not sure why not. Everything >>>> besides the engine/splash stack would go in the common bundle (not >>>> the right name) and then each engine would have its own slice. The >>>> store would combine the two pieces into the apk for delivery. We >>>> would still need to produce the apk for testing though (it looks >>>> like there is a way to pull an apk out of the bundle too). >>>> >>>> How to do this is beyond me though >>>> >>>> Thanks, >>>> Brian >>>> On Jun 14, 2019, 10:55 PM -0400, J. Landman Gay via use-livecode >>>> , wrote: >>>>> This is good to know. But what I'd really like to see is the app >>>>> bundle that the Play Store expects. I wonder if that's possible. >>>>> >>>>> -- >>>>> Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive >>>>> Software | http://www.hyperactivesw.com On June 14, 2019 9:24:24 >>>>> PM Sannyasin Brahmanathaswami via use-livecode >>>>> wrote: >>>>> >>>>> > Got it, it works... >>>>> > >>>>> > Jerry __ thanks for the chart! >>>>> > >>>>> > "Boy!" this needs to be documented somewhere... >>>>> > >>>>> > BR >>>>> > >>>>> > ?Jerry wrote >>>>> > So like this for your sequence if your highest used VC is 15 then: >>>>> > >>>>> > Build VC >>>>> > arm v7a 16 >next time --->20>next time--->24 >>>>> > arm64 17>next time--->21--->next time--->25 >>>>> > X86 18--->next time--->22--->next time--->26 >>>>> > x86-64 19--->next time--->23--->next time--->27 >>>>> > >>>>> > >>>>> > and so on, you see the 64 builds need to be higher vc then the >>>>> 32bits >>>>> > >>>>> > >>>>> > Mark (W) wrote: >>>>> > >>>>> > > I wonder if the reason this didn't work is because you have >>>>> > > the version code for armv7 > that for arm64... >>>>> > > >>>>> > > I suspect the play store will choose the highest version coded >>>>> APK >>>>> > > that will >>>>> > > run on the target device. As ARMv7 APKs will run on devices >>>>> which can >>>>> > > run ARM64, >>>>> > > it will choose the ARMv7 in preference (as it is version code >>>>> > > 14, which is greater than 7) and thus 'completely shadow' the >>>>> &
Re: Android - Different Builds
That's a good question and to which i have no answer. Op 15-6-2019 om 17:45 schreef J. Landman Gay via use-livecode: Is a combined LC app the same as the bumdle the Play Store expects? I think the Play Store extracts and sends only the parts the user needs. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 15, 2019 2:37:40 AM JJS via use-livecode wrote: you can choose yourself. You can submit a bundle (1 big apk) with different builds, or you can upload different builds per release i have opted out on Google's signing, because i don't what happens if you use their app shrinking method Op 15-6-2019 om 05:51 schreef J. Landman Gay via use-livecode: For testing we could just do what we do now, since you can distribute to testers privately. I think we'd only need the bundle when submitting to the Play Store. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 14, 2019 10:01:40 PM Brian Milby via use-livecode wrote: From reading a little about it, I’m not sure why not. Everything besides the engine/splash stack would go in the common bundle (not the right name) and then each engine would have its own slice. The store would combine the two pieces into the apk for delivery. We would still need to produce the apk for testing though (it looks like there is a way to pull an apk out of the bundle too). How to do this is beyond me though Thanks, Brian On Jun 14, 2019, 10:55 PM -0400, J. Landman Gay via use-livecode , wrote: This is good to know. But what I'd really like to see is the app bundle that the Play Store expects. I wonder if that's possible. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 14, 2019 9:24:24 PM Sannyasin Brahmanathaswami via use-livecode wrote: > Got it, it works... > > Jerry __ thanks for the chart! > > "Boy!" this needs to be documented somewhere... > > BR > > ?Jerry wrote > So like this for your sequence if your highest used VC is 15 then: > > Build VC > arm v7a 16 >next time --->20>next time--->24 > arm64 17>next time--->21--->next time--->25 > X86 18--->next time--->22--->next time--->26 > x86-64 19--->next time--->23--->next time--->27 > > > and so on, you see the 64 builds need to be higher vc then the 32bits > > > Mark (W) wrote: > > > I wonder if the reason this didn't work is because you have the > > version code > > for armv7 > that for arm64... > > > > I suspect the play store will choose the highest version coded APK > > that will > > run on the target device. As ARMv7 APKs will run on devices which can > > run ARM64, > > it will choose the ARMv7 in preference (as it is version code 14, > > which is greater > > than 7) and thus 'completely shadow' the ARM64 APK. > > > > Upshot: probably best to make sure ARM64 APKs have higher version code > > than > > ARM7 ones (the same is true of x86-64 and x86 - but in that case > > you've already > > got version-code-of(x86-64) > version-code-of(x86) which is why you > > aren't getting > > a shadowed error for those) > > > > Warmest Regards, > > > > Mark. > > > > ___ > 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 ___ 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 ___ 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 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
Re: Android - Different Builds
Is a combined LC app the same as the bumdle the Play Store expects? I think the Play Store extracts and sends only the parts the user needs. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 15, 2019 2:37:40 AM JJS via use-livecode wrote: you can choose yourself. You can submit a bundle (1 big apk) with different builds, or you can upload different builds per release i have opted out on Google's signing, because i don't what happens if you use their app shrinking method Op 15-6-2019 om 05:51 schreef J. Landman Gay via use-livecode: For testing we could just do what we do now, since you can distribute to testers privately. I think we'd only need the bundle when submitting to the Play Store. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 14, 2019 10:01:40 PM Brian Milby via use-livecode wrote: From reading a little about it, I’m not sure why not. Everything besides the engine/splash stack would go in the common bundle (not the right name) and then each engine would have its own slice. The store would combine the two pieces into the apk for delivery. We would still need to produce the apk for testing though (it looks like there is a way to pull an apk out of the bundle too). How to do this is beyond me though Thanks, Brian On Jun 14, 2019, 10:55 PM -0400, J. Landman Gay via use-livecode , wrote: This is good to know. But what I'd really like to see is the app bundle that the Play Store expects. I wonder if that's possible. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 14, 2019 9:24:24 PM Sannyasin Brahmanathaswami via use-livecode wrote: > Got it, it works... > > Jerry __ thanks for the chart! > > "Boy!" this needs to be documented somewhere... > > BR > > ?Jerry wrote > So like this for your sequence if your highest used VC is 15 then: > > Build VC > arm v7a 16 >next time --->20>next time--->24 > arm64 17>next time--->21--->next time--->25 > X86 18--->next time--->22--->next time--->26 > x86-64 19--->next time--->23--->next time--->27 > > > and so on, you see the 64 builds need to be higher vc then the 32bits > > > Mark (W) wrote: > > > I wonder if the reason this didn't work is because you have the > > version code > > for armv7 > that for arm64... > > > > I suspect the play store will choose the highest version coded APK > > that will > > run on the target device. As ARMv7 APKs will run on devices which can > > run ARM64, > > it will choose the ARMv7 in preference (as it is version code 14, > > which is greater > > than 7) and thus 'completely shadow' the ARM64 APK. > > > > Upshot: probably best to make sure ARM64 APKs have higher version code > > than > > ARM7 ones (the same is true of x86-64 and x86 - but in that case > > you've already > > got version-code-of(x86-64) > version-code-of(x86) which is why you > > aren't getting > > a shadowed error for those) > > > > Warmest Regards, > > > > Mark. > > > > ___ > 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 ___ 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 ___ 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 ___ 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
Re: Android - Different Builds
you can choose yourself. You can submit a bundle (1 big apk) with different builds, or you can upload different builds per release i have opted out on Google's signing, because i don't what happens if you use their app shrinking method Op 15-6-2019 om 05:51 schreef J. Landman Gay via use-livecode: For testing we could just do what we do now, since you can distribute to testers privately. I think we'd only need the bundle when submitting to the Play Store. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 14, 2019 10:01:40 PM Brian Milby via use-livecode wrote: From reading a little about it, I’m not sure why not. Everything besides the engine/splash stack would go in the common bundle (not the right name) and then each engine would have its own slice. The store would combine the two pieces into the apk for delivery. We would still need to produce the apk for testing though (it looks like there is a way to pull an apk out of the bundle too). How to do this is beyond me though Thanks, Brian On Jun 14, 2019, 10:55 PM -0400, J. Landman Gay via use-livecode , wrote: This is good to know. But what I'd really like to see is the app bundle that the Play Store expects. I wonder if that's possible. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 14, 2019 9:24:24 PM Sannyasin Brahmanathaswami via use-livecode wrote: > Got it, it works... > > Jerry __ thanks for the chart! > > "Boy!" this needs to be documented somewhere... > > BR > > ?Jerry wrote > So like this for your sequence if your highest used VC is 15 then: > > Build VC > arm v7a 16 >next time --->20>next time--->24 > arm64 17>next time--->21--->next time--->25 > X86 18--->next time--->22--->next time--->26 > x86-64 19--->next time--->23--->next time--->27 > > > and so on, you see the 64 builds need to be higher vc then the 32bits > > > Mark (W) wrote: > > > I wonder if the reason this didn't work is because you have the > > version code > > for armv7 > that for arm64... > > > > I suspect the play store will choose the highest version coded APK > > that will > > run on the target device. As ARMv7 APKs will run on devices which can > > run ARM64, > > it will choose the ARMv7 in preference (as it is version code 14, > > which is greater > > than 7) and thus 'completely shadow' the ARM64 APK. > > > > Upshot: probably best to make sure ARM64 APKs have higher version code > > than > > ARM7 ones (the same is true of x86-64 and x86 - but in that case > > you've already > > got version-code-of(x86-64) > version-code-of(x86) which is why you > > aren't getting > > a shadowed error for those) > > > > Warmest Regards, > > > > Mark. > > > > ___ > 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 ___ 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 ___ 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
Re: Android - Different Builds
For testing we could just do what we do now, since you can distribute to testers privately. I think we'd only need the bundle when submitting to the Play Store. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 14, 2019 10:01:40 PM Brian Milby via use-livecode wrote: From reading a little about it, I’m not sure why not. Everything besides the engine/splash stack would go in the common bundle (not the right name) and then each engine would have its own slice. The store would combine the two pieces into the apk for delivery. We would still need to produce the apk for testing though (it looks like there is a way to pull an apk out of the bundle too). How to do this is beyond me though Thanks, Brian On Jun 14, 2019, 10:55 PM -0400, J. Landman Gay via use-livecode , wrote: This is good to know. But what I'd really like to see is the app bundle that the Play Store expects. I wonder if that's possible. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 14, 2019 9:24:24 PM Sannyasin Brahmanathaswami via use-livecode wrote: > Got it, it works... > > Jerry __ thanks for the chart! > > "Boy!" this needs to be documented somewhere... > > BR > > ?Jerry wrote > So like this for your sequence if your highest used VC is 15 then: > > Build VC > arm v7a 16 >next time --->20>next time--->24 > arm64 17>next time--->21--->next time--->25 > X86 18--->next time--->22--->next time--->26 > x86-64 19--->next time--->23--->next time--->27 > > > and so on, you see the 64 builds need to be higher vc then the 32bits > > > Mark (W) wrote: > > > I wonder if the reason this didn't work is because you have the > > version code > > for armv7 > that for arm64... > > > > I suspect the play store will choose the highest version coded APK > > that will > > run on the target device. As ARMv7 APKs will run on devices which can > > run ARM64, > > it will choose the ARMv7 in preference (as it is version code 14, > > which is greater > > than 7) and thus 'completely shadow' the ARM64 APK. > > > > Upshot: probably best to make sure ARM64 APKs have higher version code > > than > > ARM7 ones (the same is true of x86-64 and x86 - but in that case > > you've already > > got version-code-of(x86-64) > version-code-of(x86) which is why you > > aren't getting > > a shadowed error for those) > > > > Warmest Regards, > > > > Mark. > > > > ___ > 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 ___ 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 ___ 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
Re: Android - Different Builds
From reading a little about it, I’m not sure why not. Everything besides the engine/splash stack would go in the common bundle (not the right name) and then each engine would have its own slice. The store would combine the two pieces into the apk for delivery. We would still need to produce the apk for testing though (it looks like there is a way to pull an apk out of the bundle too). How to do this is beyond me though Thanks, Brian On Jun 14, 2019, 10:55 PM -0400, J. Landman Gay via use-livecode , wrote: > This is good to know. But what I'd really like to see is the app bundle > that the Play Store expects. I wonder if that's possible. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > On June 14, 2019 9:24:24 PM Sannyasin Brahmanathaswami via use-livecode > wrote: > > > Got it, it works... > > > > Jerry __ thanks for the chart! > > > > "Boy!" this needs to be documented somewhere... > > > > BR > > > > ?Jerry wrote > > So like this for your sequence if your highest used VC is 15 then: > > > > Build VC > > arm v7a 16 >next time --->20>next time--->24 > > arm64 17>next time--->21--->next time--->25 > > X86 18--->next time--->22--->next time--->26 > > x86-64 19--->next time--->23--->next time--->27 > > > > > > and so on, you see the 64 builds need to be higher vc then the 32bits > > > > > > Mark (W) wrote: > > > > > I wonder if the reason this didn't work is because you have the > > > version code > > > for armv7 > that for arm64... > > > > > > I suspect the play store will choose the highest version coded APK > > > that will > > > run on the target device. As ARMv7 APKs will run on devices which can > > > run ARM64, > > > it will choose the ARMv7 in preference (as it is version code 14, > > > which is greater > > > than 7) and thus 'completely shadow' the ARM64 APK. > > > > > > Upshot: probably best to make sure ARM64 APKs have higher version code > > > than > > > ARM7 ones (the same is true of x86-64 and x86 - but in that case > > > you've already > > > got version-code-of(x86-64) > version-code-of(x86) which is why you > > > aren't getting > > > a shadowed error for those) > > > > > > Warmest Regards, > > > > > > Mark. > > > > > > > ___ > > 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 > > > > > ___ > 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
Re: Android - Different Builds
This is good to know. But what I'd really like to see is the app bundle that the Play Store expects. I wonder if that's possible. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 14, 2019 9:24:24 PM Sannyasin Brahmanathaswami via use-livecode wrote: Got it, it works... Jerry __ thanks for the chart! "Boy!" this needs to be documented somewhere... BR ?Jerry wrote So like this for your sequence if your highest used VC is 15 then: BuildVC arm v7a16 >next time --->20>next time--->24 arm6417>next time--->21--->next time--->25 X8618--->next time--->22--->next time--->26 x86-64 19--->next time--->23--->next time--->27 and so on, you see the 64 builds need to be higher vc then the 32bits Mark (W) wrote: > I wonder if the reason this didn't work is because you have the > version code > for armv7 > that for arm64... > > I suspect the play store will choose the highest version coded APK > that will > run on the target device. As ARMv7 APKs will run on devices which can > run ARM64, > it will choose the ARMv7 in preference (as it is version code 14, > which is greater > than 7) and thus 'completely shadow' the ARM64 APK. > > Upshot: probably best to make sure ARM64 APKs have higher version code > than > ARM7 ones (the same is true of x86-64 and x86 - but in that case > you've already > got version-code-of(x86-64) > version-code-of(x86) which is why you > aren't getting > a shadowed error for those) > > Warmest Regards, > > Mark. > ___ 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 ___ 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
Re: Android - Different Builds
Got it, it works... Jerry __ thanks for the chart! "Boy!" this needs to be documented somewhere... BR Jerry wrote So like this for your sequence if your highest used VC is 15 then: BuildVC arm v7a16 >next time --->20>next time--->24 arm6417>next time--->21--->next time--->25 X8618--->next time--->22--->next time--->26 x86-64 19--->next time--->23--->next time--->27 and so on, you see the 64 builds need to be higher vc then the 32bits Mark (W) wrote: > I wonder if the reason this didn't work is because you have the > version code > for armv7 > that for arm64... > > I suspect the play store will choose the highest version coded APK > that will > run on the target device. As ARMv7 APKs will run on devices which can > run ARM64, > it will choose the ARMv7 in preference (as it is version code 14, > which is greater > than 7) and thus 'completely shadow' the ARM64 APK. > > Upshot: probably best to make sure ARM64 APKs have higher version code > than > ARM7 ones (the same is true of x86-64 and x86 - but in that case > you've already > got version-code-of(x86-64) > version-code-of(x86) which is why you > aren't getting > a shadowed error for those) > > Warmest Regards, > > Mark. > ___ 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
Re: Android - Different Builds
Yes i believe it works so too as Mark says. @BR make sure that for your next release, that when now your highest versioncode is 15 for x86-64 the armv7a starts with 16 that's why i showed you the sequence as example. you need to increase the versioncodes but with the lowest versioncode for the lowest architecture, i did it too and had no problem so like this for your sequence if your highest used VC is 15 then: Build VC arm v7a 16 >next time --->20>next time--->24 arm64 17>next time--->21--->next time--->25 X86 18--->next time--->22--->next time--->26 x86-64 19--->next time--->23--->next time--->27 and so on, you see the 64 builds need to be higher vc then the 32bits Op 14-6-2019 om 10:33 schreef Mark Waddingham via use-livecode: On 2019-06-14 00:41, Sannyasin Brahmanathaswami via use-livecode wrote: Aloha Jerry, I think I have done it correctly 1) I have the four builds in one release 2) Native platforms -- armeabi-v7a - version code 14 Native platforms -- x86_64 - version code 9 Native platforms -- x86 - version code 8 Native platforms -- arm64-v8a - version code 7 I still get ERROR = 1 message for APK 7 Fully shadowed APK Problem: This APK will not be served to any users because it is completely I wonder if the reason this didn't work is because you have the version code for armv7 > that for arm64... I suspect the play store will choose the highest version coded APK that will run on the target device. As ARMv7 APKs will run on devices which can run ARM64, it will choose the ARMv7 in preference (as it is version code 14, which is greater than 7) and thus 'completely shadow' the ARM64 APK. Upshot: probably best to make sure ARM64 APKs have higher version code than ARM7 ones (the same is true of x86-64 and x86 - but in that case you've already got version-code-of(x86-64) > version-code-of(x86) which is why you aren't getting a shadowed error for those) Warmest Regards, Mark. ___ 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
Re: Android - Different Builds
On 2019-06-14 00:41, Sannyasin Brahmanathaswami via use-livecode wrote: Aloha Jerry, I think I have done it correctly 1) I have the four builds in one release 2) Native platforms -- armeabi-v7a- version code 14 Native platforms -- x86_64 - version code 9 Native platforms -- x86- version code 8 Native platforms -- arm64-v8a - version code 7 I still get ERROR = 1 message for APK 7 Fully shadowed APK Problem: This APK will not be served to any users because it is completely I wonder if the reason this didn't work is because you have the version code for armv7 > that for arm64... I suspect the play store will choose the highest version coded APK that will run on the target device. As ARMv7 APKs will run on devices which can run ARM64, it will choose the ARMv7 in preference (as it is version code 14, which is greater than 7) and thus 'completely shadow' the ARM64 APK. Upshot: probably best to make sure ARM64 APKs have higher version code than ARM7 ones (the same is true of x86-64 and x86 - but in that case you've already got version-code-of(x86-64) > version-code-of(x86) which is why you aren't getting a shadowed error for those) Warmest Regards, Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone can create apps ___ 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
Re: Android - Different Builds
Hurray! That worked: Version code 15 Native platforms arm64-v8a, armeabi-v7a. 74.9 MB Version code 9 Native platforms x86_64 64.0 MB Version code 8 Native platforms x86 63.7 MB -- No "overshowed" ERROR -- One warning about extra code in the build of Version 15. -- One warning (standard) about the last version APK deactivated Full rollout underway... Thanks Ralph! Brahmanathaswami Ralph DiMola wrote: Try making 1 build for armv7 AND arm64 ___ 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
RE: Android - Different Builds
Try making 1 build for armv7 AND arm64 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 Sannyasin Brahmanathaswami via use-livecode Sent: Thursday, June 13, 2019 6:42 PM To: How to use LiveCode Cc: Sannyasin Brahmanathaswami Subject: Re: Android - Different Builds Aloha Jerry, I think I have done it correctly 1) I have the four builds in one release 2) Native platforms -- armeabi-v7a- version code 14 Native platforms -- x86_64 - version code 9 Native platforms -- x86- version code 8 Native platforms -- arm64-v8a - version code 7 I still get 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. === I have no choice but to remove arm64-v8a, but it supports devices a lot of devices (3105) I could run it anyway and not remove it... maybe it is a "bogus" message from their AI analysis. OR arm64-v8a is now covered by one of the other three, ie. will be installed on the 3105 devices listed under arm64-v8a? BR JJB wrote 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 ___ 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
Re: Android - Different Builds
Aloha Jerry, I think I have done it correctly 1) I have the four builds in one release 2) Native platforms -- armeabi-v7a- version code 14 Native platforms -- x86_64 - version code 9 Native platforms -- x86- version code 8 Native platforms -- arm64-v8a - version code 7 I still get 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. === I have no choice but to remove arm64-v8a, but it supports devices a lot of devices (3105) I could run it anyway and not remove it... maybe it is a "bogus" message from their AI analysis. OR arm64-v8a is now covered by one of the other three, ie. will be installed on the 3105 devices listed under arm64-v8a? BR JJB wrote 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 ___ 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
Re: Android - Different Builds
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 rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@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" 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@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 ___ 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
RE: Android - Different Builds
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 rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@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@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@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 ___ 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
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" 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@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
Re: Android - Different Builds
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" 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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Android - Different Builds
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" wrote: OK! That's what we need hear. Thanks Ralph! On 6/12/19, 12:17 PM, "Ralph DiMola" 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@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 ___ 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
Re: Android - Different Builds
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" wrote: OK! That's what we need hear. Thanks Ralph! On 6/12/19, 12:17 PM, "Ralph DiMola" 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@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
Re: Android - Different Builds
OK! That's what we need hear. Thanks Ralph! On 6/12/19, 12:17 PM, "Ralph DiMola" 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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
RE: Android - Different Builds
This is a warning. I have not yet tested if using 4 apks will eliminate this warning. It might. This is a new warning message in the last month. 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 Sannyasin Brahmanathaswami via use-livecode Sent: Wednesday, June 12, 2019 6:13 PM To: How to use LiveCode Cc: Sannyasin Brahmanathaswami Subject: Re: Android - Different Builds Hmmm Google says 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. App download size: 101 MB Verses the previous one at 63.6 MB 38MB increase! No new app contentit all the different architectures. How can we use the "Android App Bundle" ?? Never mind, I check all four, got one .APK and uploaded... and not I see Native Platform 4 Wow, congrats to LC to doing that so easily.. BR ___ 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
RE: Android - Different Builds
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. 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 Sannyasin Brahmanathaswami via use-livecode Sent: Wednesday, June 12, 2019 6:01 PM To: How to use LiveCode Cc: Sannyasin Brahmanathaswami Subject: Re: Android - Different Builds Never mind, I check all four, got one .APK and uploaded... and not I see Native Platform 4 Wow, congrats to LC to doing that so easily.. BR On 6/12/19, 11:45 AM, "use-livecode on behalf of Sannyasin Brahmanathaswami via use-livecode" wrote: Can anyone give a short lesson on how to submit the multiple android builds on Google Release Management dashboard? All brand new to me…. BR ___ 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
Re: Android - Different Builds
Hmmm Google says 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. App download size: 101 MB Verses the previous one at 63.6 MB 38MB increase! No new app contentit all the different architectures. How can we use the "Android App Bundle" ?? Never mind, I check all four, got one .APK and uploaded... and not I see Native Platform 4 Wow, congrats to LC to doing that so easily.. BR ___ 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
Re: Android - Different Builds
Never mind, I check all four, got one .APK and uploaded... and not I see Native Platform 4 Wow, congrats to LC to doing that so easily.. BR On 6/12/19, 11:45 AM, "use-livecode on behalf of Sannyasin Brahmanathaswami via use-livecode" wrote: Can anyone give a short lesson on how to submit the multiple android builds on Google Release Management dashboard? All brand new to me…. BR ___ 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
Android - Different Builds
Can anyone give a short lesson on how to submit the multiple android builds on Google Release Management dashboard? All brand new to me…. BR ___ 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
