Recent

Author Topic: [LAMW] Using App Bundles instead of APKs  (Read 981 times)

pasquale

  • Sr. Member
  • ****
  • Posts: 254
    • Esposito Software
[LAMW] Using App Bundles instead of APKs
« on: January 24, 2021, 07:19:07 pm »
Is LAMW/Laz4Android going to support the new app bundles requested by Google Play?
« Last Edit: January 26, 2021, 04:29:11 pm by pasquale »
Apple loves breaking backward compatibility to make money. If you want to be sure that your apps will never stop working, use Windows and trash macOS!

jmpessoa

  • Hero Member
  • *****
  • Posts: 1785
Re: Using App Bundles instead of APKs
« Reply #1 on: January 24, 2021, 08:38:02 pm »

Yes!
Lamw: Lazarus Android Module Wizard
https://github.com/jmpessoa/lazandroidmodulewizard

pasquale

  • Sr. Member
  • ****
  • Posts: 254
    • Esposito Software
Re: [LAMW] Using App Bundles instead of APKs
« Reply #2 on: January 26, 2021, 03:15:49 pm »

Yes!

Great!

In what way can we create a new app bundle with LAMW? Is this function already available or will it be implemented later this year?

Thanks
Apple loves breaking backward compatibility to make money. If you want to be sure that your apps will never stop working, use Windows and trash macOS!

jmpessoa

  • Hero Member
  • *****
  • Posts: 1785
Re: Using App Bundles instead of APKs
« Reply #3 on: January 26, 2021, 03:33:41 pm »


Today or tomorrow [I need to do some tests ...]  I will update LAMW github

Then you will can do:

Quote
"Tools"  --> "[LAMW] ..." --> "'Build Release Signed Bundle ...'"

To get your  bundle..
Lamw: Lazarus Android Module Wizard
https://github.com/jmpessoa/lazandroidmodulewizard

pasquale

  • Sr. Member
  • ****
  • Posts: 254
    • Esposito Software
Re: Using App Bundles instead of APKs
« Reply #4 on: January 26, 2021, 04:11:30 pm »


Today or tomorrow [I need to do some tests ...]  I will update LAMW github

Then you will can do:

Quote
"Tools"  --> "[LAMW] ..." --> "'Build Release Signed Bundle ...'"

To get your  bundle..

Wonderful! I can't wait!
Apple loves breaking backward compatibility to make money. If you want to be sure that your apps will never stop working, use Windows and trash macOS!

rsu333

  • New Member
  • *
  • Posts: 18
Re: Using App Bundles instead of APKs
« Reply #5 on: January 26, 2021, 04:34:07 pm »
Really thanks for your activity LAMW [jmpessoa]. I suggest in tool where you keep information of path of sdk,ndk,ant, etc ,please add keys which publisher want. Secondly keep release mode option [debugging=false
in manifest .I am proud of your work as LAMW is simplest RAD ,but when we go to publisher , we face some problem which are difficult to us.
Thanks a lot .

jmpessoa

  • Hero Member
  • *****
  • Posts: 1785
Re: [LAMW] Using App Bundles instead of APKs
« Reply #6 on: January 26, 2021, 05:22:56 pm »
Quote
but when we go to publisher , we face some problem which are difficult to us.

No more....

Develop your application "normally" .... [default is debug....]

Do not worry  about release and signing  in development  mode....

When your application is "ready"  then 
LAMW will generate the "publisher"  [release/signed]  version for you:


Quote
"Tools"  --> "[LAMW] ..." --> "'Build Release Signed Apk ... ...'"

or

Quote
"Tools"  --> "[LAMW] ..." --> "'Build Release Signed Bundle ...'"


Lamw: Lazarus Android Module Wizard
https://github.com/jmpessoa/lazandroidmodulewizard

pasquale

  • Sr. Member
  • ****
  • Posts: 254
    • Esposito Software
Re: [LAMW] Using App Bundles instead of APKs
« Reply #7 on: January 26, 2021, 05:46:43 pm »
Quote
"Tools"  --> "[LAMW] ..." --> "'Build Release Signed Bundle ...'"

Please inform us when the function "Build Release Signed Bundle" is implemented, so we can update LAMW.

Shall we need to install everything from scratch of will it be enough to overwrite some files and then rebuild the Android module wizard package?

Thanks
Apple loves breaking backward compatibility to make money. If you want to be sure that your apps will never stop working, use Windows and trash macOS!

jmpessoa

  • Hero Member
  • *****
  • Posts: 1785
Re: [LAMW] Using App Bundles instead of APKs
« Reply #8 on: January 27, 2021, 06:48:17 pm »
Done!!!

NEW  "Build Release Signed Bundle"!

"Tools"  --> "[LAMW] ..." --> "Build Release Signed Bundle"

Quote
will it be enough to overwrite some files and then rebuild the Android module wizard package?

Well, you can try update the changed files and re-install the packages....   [see picture...]
[But, what about a github desktop client? so you can synchronize your system....]
Lamw: Lazarus Android Module Wizard
https://github.com/jmpessoa/lazandroidmodulewizard

pasquale

  • Sr. Member
  • ****
  • Posts: 254
    • Esposito Software
Re: [LAMW] Using App Bundles instead of APKs
« Reply #9 on: January 27, 2021, 07:41:04 pm »
Done!!!

NEW  "Build Release Signed Bundle"!

"Tools"  --> "[LAMW] ..." --> "Build Release Signed Bundle"

Quote
will it be enough to overwrite some files and then rebuild the Android module wizard package?

Well, you can try update the changed files and re-install the packages....   [see picture...]
[But, what about a github desktop client? so you can synchronize your system....]

Great!

I've just downloaded lazandroidmodulewizard-master.zip from github.

What is the normal correct way to update LAMW on my PC?

Thank you very much.

Apple loves breaking backward compatibility to make money. If you want to be sure that your apps will never stop working, use Windows and trash macOS!

jmpessoa

  • Hero Member
  • *****
  • Posts: 1785
Re: [LAMW] Using App Bundles instead of APKs
« Reply #10 on: January 27, 2021, 07:46:27 pm »
There are many....

"github desktop client"  is my favorite... 

Quote
I've just downloaded lazandroidmodulewizard-master.zip from github.

Yes, it work!

And you can use "LAMW Manager"  to update your LAMW system,  too... 
Lamw: Lazarus Android Module Wizard
https://github.com/jmpessoa/lazandroidmodulewizard

pasquale

  • Sr. Member
  • ****
  • Posts: 254
    • Esposito Software
Re: [LAMW] Using App Bundles instead of APKs
« Reply #11 on: January 27, 2021, 08:25:40 pm »
There are many....

"github desktop client"  is my favorite... 

Quote
I've just downloaded lazandroidmodulewizard-master.zip from github.

Yes, it work!

And you can use "LAMW Manager"  to update your LAMW system,  too...

Thanks.

I completed the update using lamw_manager.bat in the LAMW folder.

I created a sample project and selected "Build Release Signed Bundle" and I got the file AppLAMWProject2.aab as you can see in the attached files.

Question 1: Is the .aab file the only one that needs to be uploaded to the Google Play Store?

Question 2: Do we need to build the .aab twice in order to have both the 32 and the 64 bit versions of the app in the bundle? In other words, I wonder if we need to act as follows: (1) build a 32-bit .apk and then build the .aab; (2) build a 64 bit .apk and then build the .aab a second time.

Question 3: Considering that the Target Api is equal to 30 (as you can see in the attached project window), is the .aab file  that we can create today already compliant with those requirements that Google will impose after August 2021 for publication on the Play Store? Or shall we have to install something else?

Thanks again, jmpessoa. You are doing a great job!
« Last Edit: January 27, 2021, 09:09:23 pm by pasquale »
Apple loves breaking backward compatibility to make money. If you want to be sure that your apps will never stop working, use Windows and trash macOS!

jmpessoa

  • Hero Member
  • *****
  • Posts: 1785
Re: [LAMW] Using App Bundles instead of APKs
« Reply #12 on: January 27, 2021, 10:33:55 pm »
You need [at least] two "build" to produce a 32 and a 64 bits "libcontrols.so" 

After the first "Run" -- > "build"

You can configure here:

"Project"  ---> "Project Options"   -->  "[LAMW] ...."  --> [TAB] "Build"  --> "Chipset"

then execute a "Run" --> "Build"   again

Now you have  two  (or more)  "libcontrols.so"  !!!

LAMW will put its here [ex.]:

".....libs/armeabi-v7a"    <----32
".....libs/arm64-v8a"        <----64     (for aarch64)

So you "bundle" will be ok for google requirements ....
Lamw: Lazarus Android Module Wizard
https://github.com/jmpessoa/lazandroidmodulewizard

pasquale

  • Sr. Member
  • ****
  • Posts: 254
    • Esposito Software
Re: [LAMW] Using App Bundles instead of APKs
« Reply #13 on: January 28, 2021, 05:11:38 pm »
You need [at least] two "build" to produce a 32 and a 64 bits "libcontrols.so" 

After the first "Run" -- > "build"

You can configure here:

"Project"  ---> "Project Options"   -->  "[LAMW] ...."  --> [TAB] "Build"  --> "Chipset"

then execute a "Run" --> "Build"   again

Now you have  two  (or more)  "libcontrols.so"  !!!

LAMW will put its here [ex.]:

".....libs/armeabi-v7a"    <----32
".....libs/arm64-v8a"        <----64     (for aarch64)

So you "bundle" will be ok for google requirements ....

Thanks a lot.

So, if I understand correctly, I must proceed in the following way:

  • I must set the Chipset=32 bit (example: ARMv7a+VFPv3), click on Run-->Compile and then on Run-->Build
  • I must set the Chipset=64 bit (example: Aarch64), click again on Run-->Compile and then on Run-->Build
  • I must click on Tools-->[LAMW] Android Module Wizard-->Build Release Signed Apk

At this point I get the .aab file in the ...build\outputs\bundle\release folder, which is ready to be uploaded to the Google Play Store.

Is the .aab file that we can create today already compliant with those requirements that Google will impose after August 2021 for publication on the Play Store? Or shall we have to install something else in the future? (e.g. a new set of Api)

Thanks again
« Last Edit: January 28, 2021, 05:26:26 pm by pasquale »
Apple loves breaking backward compatibility to make money. If you want to be sure that your apps will never stop working, use Windows and trash macOS!

jmpessoa

  • Hero Member
  • *****
  • Posts: 1785
Re: [LAMW] Using App Bundles instead of APKs
« Reply #14 on: January 28, 2021, 05:40:19 pm »

Quote
Is the .aab file that we can create today already compliant with those requirements that Google will impose after August 2021 for publication on the Play Store? Or shall we have to install something else in the future?

Yes!

Quote
(e.g. a new set of Api)

Today,  you need set target Api = 29  to store App in "google play"




Lamw: Lazarus Android Module Wizard
https://github.com/jmpessoa/lazandroidmodulewizard

 

TinyPortal © 2005-2018