Other B4A v13.4 is available for download

Status
Not open for further replies.

Erel

B4X founder
Staff member
Licensed User
Longtime User
I'm happy to release a new version of B4A. The prepackaged Android SDK has been updated and is based on the current latest versions of all resources and Android SDK 36.
The handling of SDK resources was improved.

1752651774740.png


The built-in themes were updated with the new edge-to-edge feature disabled by default (https://www.b4x.com/android/forum/t...t-of-edge-to-edge-enforcement.167109/#content).

Please download the updated command line tools and prepackaged resources: https://www.b4x.com/b4a.html


Notes:

1. Crashlytics instructions updated: https://www.b4x.com/android/forum/threads/crashlytics-crash-reports.87510/#content
2. ExoPlayer is an internal library. The additional dependencies should be downloaded from: https://www.b4x.com/android/forum/threads/exoplayer-media3-video-player.158204/#content
3. The prepackaged resources should include all resources most developers need, including for Firebase and ML-Kit sdks.
 

ema01

Active Member
Licensed User
Longtime User
Hi erel, do we need to update the resources even if we had the beta installed?

The built-in themes were updated with the new edge-to-edge feature disabled by default
I've seen this suggested elsewhere in the forum.
Any particular reason?
Because it's being phased out soon, and there are already android 16 devices in the wild (my pixel 8A for example, and i'm not in the beta program)

I decided to bite the bullet and use the equivalent of "safe area inset" described here

and it seems to be working fine on all my apps so far
 
Upvote 0

Erel

B4X founder
Staff member
Licensed User
Longtime User
Upvote 0

hanyelmehy

Well-Known Member
Licensed User
Longtime User
in 13.4 B4A Bridge not connect over wifi
Notes
Same every thing was work fine with 13.3 ,i just install 13.4
 
Upvote 0

Peter Simpson

Expert
Licensed User
Longtime User
#AdditionalJar: com.google.android.ump:user-messaging-platformok
Please note, I have absolutely no idea about this, but should you have 'ok' at the end of that line. Once again, I'm just asking as I've never used that before, it just looks odd to me???

I'm happy to release a new version of B4A.
Thank you Erel, I've installed some apps on my Android 16 phones with absolutely no issues whatsoever 👍
 
Upvote 0

ac9ts

Active Member
Licensed User
Longtime User
Are there any other enhancements besides the SDK change? As someone that only writes in-house code (no Play Store stuff), is there a real reason why I should switch from v13.30 at this time?
 
Upvote 0

Erel

B4X founder
Staff member
Licensed User
Longtime User
You can stay with v13.3 for now, though the recommended version is 13.4. Updates libraries, tutorials and code snippets are based on the latest version and you might encounter issues related to outdated resources.

If you are using "heavy dependent" features such as Firebase, ML Kit and others then it is probably a good idea to upgrade soon.
 
Upvote 0

marcick

Well-Known Member
Licensed User
Longtime User
I followed the instruction "Please download the updated command line tools and prepackaged resources" but after updating to 13.4 I have this compile error:
I deleted also the object folder before compile.

B4X:
ObfuscatorMap.txt file created in Objects folder.
Compiling layouts code.    (0.02s)
Organizing libraries.    (0.00s)
    (AndroidX SDK)
Compiling resources    (0.08s)
Linking resources    Error
AndroidManifest.xml:240: error: resource style/Theme.Hidden (aka it.cc.app:style/Theme.Hidden) not found.
AndroidManifest.xml:248: error: resource style/Theme.Hidden (aka it.cc.app:style/Theme.Hidden) not found.
AndroidManifest.xml:256: error: resource style/Theme.PlayCore.Transparent (aka it.cc.app:style/Theme.PlayCore.Transparent) not found.
error: failed processing manifest.

In my manifest editor theme.hidden is not present, but I see it opening manifest.xml

B4X:
                <activity
                    android:name="androidx.credentials.playservices.HiddenActivity"
                    android:configChanges="orientation|screenSize|screenLayout|keyboardHidden"
                    android:enabled="true"
                    android:exported="false"
                    android:fitsSystemWindows="true"
                    android:theme="@style/Theme.Hidden" >
                </activity>
                <activity
                    android:name="androidx.credentials.playservices.IdentityCredentialApiHiddenActivity"
                    android:configChanges="orientation|screenSize|screenLayout|keyboardHidden"
                    android:enabled="true"
                    android:exported="false"
                    android:fitsSystemWindows="true"
                    android:theme="@style/Theme.Hidden" >
                </activity>
 
Upvote 0

drgottjr

Expert
Licensed User
Longtime User
If you are using "heavy dependent" features such as Firebase, ML Kit and others then it is probably a good idea to upgrade soon.
for what it's worth, that would be me. have upgraded. starting to run test. noticed this warning: generated classes.zip is too small! (see below)

B4X:
Dex: C:\Android\tools\..\extras\b4a_remote\androidx\annotation\annotation\1.9.1\annotation-1.9.1    (0.91s)
    WARNING: generated classes.zip is too small!
c:\android\tools\..\extras\b4a_remote\androidx\annotation\annotation\1.9.1\annotation-1.9.1.zip
Dex: C:\Android\tools\..\extras\b4a_remote\androidx\annotation\annotation-jvm\1.9.1\annotation-jvm-1.9.1    (1.66s)
Dex: org.jetbrains.kotlin-kotlin-stdlib    (14.64s)
Dex: org.jetbrains.kotlinx-kotlinx-coroutines-android    (1.88s)
Dex: C:\Android\tools\..\extras\b4a_remote\androidx\lifecycle\lifecycle-common\2.9.1\lifecycle-common-2.9.1    (0.90s)
    WARNING: generated classes.zip is too small!
c:\android\tools\..\extras\b4a_remote\androidx\lifecycle\lifecycle-common\2.9.1\lifecycle-common-2.9.1.zip
Dex: C:\Android\tools\..\extras\b4a_remote\androidx\lifecycle\lifecycle-common-jvm\2.9.1\lifecycle-common-jvm-2.9.1    (2.55s)
Dex: org.jetbrains.kotlinx-kotlinx-coroutines-core-jvm    (9.01s)
Dex: C:\Android\tools\..\extras\b4a_remote\androidx\collection\collection\1.5.0\collection-1.5.0    (0.91s)
    WARNING: generated classes.zip is too small!
 
Upvote 0

Alessandro71

Well-Known Member
Licensed User
Longtime User
are there any changes regarding OkHttp POST behaviour in this release?
I'm currently having some strange issues, that may be caused by some server IPS system (Imunify360) but not really sure, and wishing to rule out any other changes...
 
Upvote 0

Lucian Gontila

Member
Licensed User
Longtime User
I'm trying to upload a new version but keep getting this error:
"Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again. Your App Bundle is expected to be signed with the certificate with fingerprint:
SHA1: ED:91:7C...
but the certificate used to sign the App Bundle you uploaded has fingerprint:
SHA1: 7B:EC:70...".
I have multiple keystore files for various apps but I'd checked them and none of them has SHA1: ED:91:7C... so it's not about using the wrong key.
I have uploaded a previous version of the app just 4 days ago and everything worked just fine. I've just updated to v13.40, latest commandlinetools-win, resources, android-36 and jdk-19.0.2.
Please can you tell me what is wrong and how can I solve that?
 
Upvote 0

Cableguy

Expert
Licensed User
Longtime User
I'm trying to upload a new version but keep getting this error:
"Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again. Your App Bundle is expected to be signed with the certificate with fingerprint:
SHA1: ED:91:7C...
but the certificate used to sign the App Bundle you uploaded has fingerprint:
SHA1: 7B:EC:70...".
I have multiple keystore files for various apps but I'd checked them and none of them has SHA1: ED:91:7C... so it's not about using the wrong key.
I have uploaded a previous version of the app just 4 days ago and everything worked just fine. I've just updated to v13.40, latest commandlinetools-win, resources, android-36 and jdk-19.0.2.
Please can you tell me what is wrong and how can I solve that?
This means you are using the wrong key to sign your bundle (previous versions must have been signed with a different key)
If the problem persists please start a new thread
 
Upvote 0

Alessandro71

Well-Known Member
Licensed User
Longtime User
are there any changes regarding OkHttp POST behaviour in this release?
I'm currently having some strange issues, that may be caused by some server IPS system (Imunify360) but not really sure, and wishing to rule out any other changes...
just writing as a followup: no issues with OkHttp in this release, problem was elsewhere
 
Upvote 0

Sganga61

Member
Licensed User
Longtime User
I'm happy to release a new version of B4A. The prepackaged Android SDK has been updated and is based on the current latest versions of all resources and Android SDK 36.
The handling of SDK resources was improved.

View attachment 165409

The built-in themes were updated with the new edge-to-edge feature disabled by default (https://www.b4x.com/android/forum/t...t-of-edge-to-edge-enforcement.167109/#content).

Please download the updated command line tools and prepackaged resources: https://www.b4x.com/b4a.html


Notes:

1. Crashlytics instructions updated: https://www.b4x.com/android/forum/threads/crashlytics-crash-reports.87510/#content
2. ExoPlayer is an internal library. The additional dependencies should be downloaded from: https://www.b4x.com/android/forum/threads/exoplayer-media3-video-player.158204/#content
3. The prepackaged resources should include all resources most developers need, including for Firebase and ML-Kit sdks.

HI
try to using Android35 or Android35-ext15 along with B4A 13.40 version I still get this error during compilation. The app works fine with Android 34

aapt2.exe E 07-18 13:31:35 16324 24108 LoadedArsc.cpp:94] RES_TABLE_TYPE_TYPE entry offsets overlap actual entry data.
aapt2.exe E 07-18 13:31:35 16324 24108 ApkAssets.cpp:149] Failed to load resources table in APK 'F:\Android\platforms\android-35-ext15\android.jar'.
error: failed to load include path F:\Android\platforms\android-35-ext15\android.jar.
 
Upvote 0
Status
Not open for further replies.
Top