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.
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
Hi, There is this warning in the Play Console: 2 actions recommended Your app no longer uses supported APIs or parameters for borderless display At least one of the APIs or parameters you are using and for which you have specified the use of borderless and window display has been...
www.b4x.com
and it seems to be working fine on all my apps so far
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???
This is most likely not related to the new version as nothing has changed in regards to B4A-Bridge, however please start a new thread for further discussion.
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?
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.
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
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...
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?
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
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...
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.
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.