Other B4A v10.7 BETA is available for download

[Erel]

*** This is a real beta version. More "beta" than the last few updates. ***

In the last couple of years, Google made many changes to Android, quite complex, building toolchain. With a few workarounds, it was possible to keep using the older tools, but at this point we have reached their limits.

This update replaces several components of the underlying tools (AAPT2, APKSigner and AAB bundle tool).
It solves all kinds of limitations including:

• Support for signing scheme v2, which is required when setting targetSdkVersion to 30.
• Support for building app bundles. This type of package will be required by Google Play, for new apps, later this year.
• Support for newer versions of SDK resources.

It can also provide some performance improvements.

These are under the hood changes. The behavior should be exactly as before.

Bundles - AAB

There is a new build bundle option:

There is no reason to build bundles (AABs) except for Google Play submissions.
You need to download bundletool.jar and put it in <android sdk>\tools\bin

Beta: www.b4x.com/android/files/beta.exe

 

[Erel]

Beta #2 is available for download. Same link as before.

It fixes an issue with #AdditionalRes.

 

[Negative Impact]

hi erel
thank you for working on this update

im update to this version and show me error while try to build my project
This source was running in the previous version without any problems

 

[Erel]

Please start a new thread. Post the error as text and provide more information.

 

[PuzzleTak]

hi erel
thank you for working on this update

im update to this version and show me error while try to build my project
This source was running in the previous version without any problems

View attachment 109117

When I installed b4a 10.7 beta, the project I ran got an error from my resources, but I have no problem with b4a 10.6

 

[Erel]

Start a new thread and provide more information.

 

[MarcoRome]

• Support for signing scheme v2, which is required when setting targetSdkVersion to 30.
• Support for building app bundles. This type of package will be required by Google Play, for new apps, later this year.

I read ( https://developer.android.com/distribute/best-practices/develop/target-sdk )

Starting in November 2021, app updates will be required to target API level 30 or above and adjust for behavioral changes in Android 11. Existing apps that are not receiving updates are unaffected and can continue to be downloaded from the Play Store.

The switch to Android App Bundle delivery will also impact instant experiences using the legacy Instant app ZIP format. From August 2021, new instant experiences and updates to existing instant experiences will be required to publish instant-enabled app bundles.

So if i understand correctly the AAB will be mandatory from August 2021 and SDK 30 from November 2021

 

[Erel]

You can see the requirements here: https://android-developers.googleblog.com/2020/11/new-android-app-bundle-and-target-api.html
AAB will be required for new apps only, starting from August 2021.

 

[MarcoRome]

You can see the requirements here: https://android-developers.googleblog.com/2020/11/new-android-app-bundle-and-target-api.html
AAB will be required for new apps only, starting from August 2021.

ok, then this is wrong ".. new instant experiences and updates to existing instant experiences will be required to publish instant-enabled app bundles. ..."
Thanks @Erel

 

[Erel]

It is not wrong. It talks about instant apps which are different than regular apps.

 

[MarcoRome]

It is not wrong. It talks about instant apps which are different than regular apps.

right "instant apps"

 

[tsteward]

• Support for building app bundles. This type of package will be required by Google Play, for new apps, later this year.

Does this mean we MUST also use App Signing?

 

[Erel]

See post #8.

AAB does require opting into Google signing method.

 

[Erel]

Beta #3 released.
www.b4x.com/android/files/beta.exe

- Fixes an issue with subfolders inside the Files folder.
- New #SignKeyAlgorithm attribute.
- New AAB automatic conditional symbol.

If you opt-in to Google signing option with an existing app then you don't need to do anything special, other than the extraction of the private key once.
With a new app, you need to sign the bundle file (AAB) with a different key, the upload key. It can be done with:

#if AAB
    #SignKeyFile: my-release-key.jks
    #SignKeyPassword: xxxxxxx
    #SignKeyAlgorithm: -digestalg SHA1 -sigalg SHA256withRSA
#end if

 

[MarcoRome]

Beta #3 released.
www.b4x.com/android/files/beta.exe

- Fixes an issue with subfolders inside the Files folder.
- New #SignKeyAlgorithm attribute.
- New AAB automatic conditional symbol.

If you opt-in to Google signing option with an existing app then you don't need to do anything special, other than the extraction of the private key once.
With a new app, you need to sign the bundle file (AAB) with a different key, the upload key. It can be done with:

#if AAB
    #SignKeyFile: my-release-key.jks
    #SignKeyPassword: xxxxxxx
    #SignKeyAlgorithm: -digestalg SHA1 -sigalg SHA256withRSA
#end if

Is possibile enter the key of the app used for the signature type:

#SignKeyFile: my-release-key.keystore

?

 

[Erel]

Not sure that I understand...

 

[MarcoRome]

Not sure that I understand...

Pls @Erel look this thread: https://www.b4x.com/android/forum/threads/google-play-app-signing-and-jks.128406/

 

[kisoft]

These links from the first post do not work for me - how to get around it ...

 

[MarcoRome]

These links from the first post do not work for me - how to get around it ...

Click right button mouse and choose save

 

[Informatix]

Fixes for the french localization of menus:
"Configuer les chemins" should be "Configurer les chemins"
"Run AVD Manager" should be "Exécuter AVD Manager" ou "Lancer AVD Manager"
The second entry for "Sauvegarde automatique" could be "Archivage automatique" ou "Sauvegarde des versions" to avoid ambiguity (I see there's the same ambiguity in english)