...@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 ha
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...@h
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
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-
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 B
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 t
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 us
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
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
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 pla
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 bui
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
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 -
ia 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
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, eac
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
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
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
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.
Resolu
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. Uplo
-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
nathaswami
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&qu
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
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 subm
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 a
25 matches
Mail list logo
