Other B4A v10.7 is available for download

Status
Not open for further replies.

Erel

B4X founder
Staff member
Licensed User
Longtime User
Download link: https://www.b4x.com/b4a.html

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:

1614076659519-png.108598


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

A new attribute named #SignKeyAlgorithm was added together with a new automatic conditional compilation symbol - AAB, they can be used in cases where the AAB signing key is different than the standard key. This is relevant for new apps:
B4X:
#if AAB
    #SignKeyFile: my-release-key.jks
#SignKeyPassword: xxxxxxx
#SignKeyAlgorithm: -digestalg SHA1 -sigalg SHA256withRSA
#end if

There are some old third party libraries that are not compatible with the new toolchain (DesignSupport for example). If your project depends on such library then you can keep a copy of B4A 10.6. B4A 10.6 is not compatible with targetSdkVersion=30 so it is only a temporary solution.


B4A 10.7 depends on a recent version of the build tools. If you get an error similar to:

Signing package file (debug key). Error
Unsupported option: --v3-signing-enabled. See --help for supported options.

Then you are using an old version of Android SDK and need to upgrade. It is very simple to upgrade the SDK: https://www.b4x.com/b4a.html

Download link: https://www.b4x.com/b4a.html
 
Last edited:

scsjc

Well-Known Member
Licensed User
Longtime User
Is it necessary the ... manifest-> targetSdkVersion to 30 ... to be able to upload to playstore with AAB format? or does it also work with manifest-> targetSdkVersion to 29?
 
Upvote 0

scsjc

Well-Known Member
Licensed User
Longtime User
It is very simple with an existing app:

1. Opt-in to Google signing key feature.
2. Follow their instructions with pepk.jar (you will see it).
3. Build an app bundle and upload it.

A new app will require an additional step (with the #IF AAB).
Everything will be explained, including how to test it with the bundletool.
Yes Really Super EASY, i upload the old app in AAB format, and work perfectly :) thanks for your great work
 
Upvote 0

hatzisn

Expert
Licensed User
Longtime User
I cannot download bundletool.jar. I click on it and nothing is downloaded. I right click to open it in a new tab in case it is http download in https page and cannot be loaded but again I am not able to download anything. Is something wrong?
 
Upvote 0

agraham

Expert
Licensed User
Longtime User
Why is JDK1.8's 211 build still recommended.
One reason is that Android's Java dialect is based on Java 7 so there is no point in using a later version. Also jars compiled with Java 8 can be run by later Javas but the converse in not true.
 
Upvote 0

free2end

Member
Licensed User
I want to use B4A 10.6.
In b4x.com, is there a page with older-previous versions of B4A to download?
Please help me find the correct file for downloading...

many, many thanks...
 
Upvote 0
Status
Not open for further replies.
Top