Other B4A v13.40 BETA - with a shiny new SDK

Status
Not open for further replies.

Erel

B4X founder
Staff member
Licensed User
Longtime User
I'm happy to release a new beta 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.

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).

Installation instructions:

1. B4A - https://www.b4x.com/android/files/beta.exe
2. Download latest version of Android command line tools: https://developer.android.com/studio/index.html#command-line-tools-only
Unpack it in a new folder.
3. Download the prepackaged resources: https://www.b4x.com/android/files/resources_7_25.zip
The resources are also available on github: https://github.com/AnywhereSoftware/B4A/releases/tag/7_25

Best to use a tool such as 7zip to unpack it: https://www.7-zip.org/

The Android SDK folder should look like:
1751897810993.png

4. Set the path of android.jar (Tools - Configure Paths): <android sdk>\platforms\android-36\android.jar

Note that ExoPlayer is an internal library now.
The prepackaged resources should include all resources most developers need, including for Firebase and ML-Kit sdks.
No need to run B4A-SdkManager, unless a resource is missing.

Notes:

1. If using crashlytics then update the #AdditionalJar list: https://www.b4x.com/android/forum/threads/crashlytics-crash-reports.87510/#content
 
Last edited:

Flavio SOuza

Member
Licensed User
Longtime User
Hi everyone,

I recently updated to the latest B4A beta version with support for SDK 35. However, I'm encountering an error with the AdsHelper library when trying to use fetchopenerad. The stack trace points to issues with java.lang.reflect.Method.invoke and anywheresoftware.b4a.shell during runtime. I’ve configured the SDK 35 path and updated dependencies via the B4A SDK Manager, but the issue persists.


Could anyone help identify the cause or suggest fixes? Thanks!


helpb4a.png
 
Upvote 0

asales

Expert
Licensed User
Longtime User
Hi everyone,
(...)
Could anyone help identify the cause or suggest fixes? Thanks!
Hi Flavio.
1 - Is always better to create a new thread to this kind of issue.
2 - Try this lib from @Jack Cole. It worked to me with the new version and SDK:
 
Upvote 0

Erel

B4X founder
Staff member
Licensed User
Longtime User
Upvote 0

Tomas Petrus

Active Member
Licensed User
Longtime User
I'm happy to release a new beta 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.

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).

What does it mean exactly for aps made for sdk35 with described changes to opt out edge-to-edge implemented ?
Leave manifest as it is or reverse it back to pre 35 ?
 
Upvote 0

Tomas Petrus

Active Member
Licensed User
Longtime User
I don’t have android 16… and have already report from client that App that has edge to edge opted in sdk35 version now builded in new ide for sdk36 is broken that meens that esge to edge is not opted on android 16. Please help.
 
Upvote 0

mcqueccu

Well-Known Member
Licensed User
Longtime User
I don’t have android 16… and have already report from client that App that has edge to edge opted in sdk35 version now builded in new ide for sdk36 is broken that meens that esge to edge is not opted on android 16. Please help.
In your Manifest, the Target SDK version should be 35. This is the recommended version from Google for now NOT 36. If you set it to 36, Edge to Edge will be broken on devices running Android 16

1763723500139.png


Also Refer to this
 
Last edited:
Upvote 0
Status
Not open for further replies.
Top