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:

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:
Sort by date Sort by votes

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!


 
Upvote 0

asales

Expert
Licensed User
Longtime User
Flavio SOuza said:
Hi everyone,
(...)
Could anyone help identify the cause or suggest fixes? Thanks!
Click to expand...
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:

AdsHelper Extension for Traditional B4A apps & more

I wanted to share an update I made to the AdsHelper class and example. Added: support for rewarded video ads events for rewarded video events for rewarded interstitial events for open ads added parameter for open ads for setting the background delay before allowing the ad to show incorporated...
www.b4x.com
 
Upvote 0

Erel

B4X founder
Staff member
Licensed User
Longtime User
Upvote 0
T

Tomas Petrus

Active Member
Licensed User
Longtime User

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
T

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

Expert
Licensed User
Longtime User
Tomas Petrus said:
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.
Click to expand...
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



Also Refer to this

B4A v13.4 still forcing Edge-to-Edge

I have installed v13.4 with no problems but the Edge-to-Edge enforcement is still in effect. I think it may be my legacy Manifest 'light theme' which you can see in the manifest code below: 'This code will be applied to the manifest file during compilation. 'You do not need to modify it in...
www.b4x.com
 
Last edited:
Upvote 0
Status
Not open for further replies.

Similar Threads

  • Locked
  • Question
Android Question B4A v13.4 still forcing Edge-to-Edge
Replies
4
Views
2K
Erel
  • Locked
  • Question
Beta B4A v13.3 BETA is available for download
Replies
11
Views
3K
asales
  • Question
Android Question B4A v13.0 BETA - error to compile with the new SDK
Replies
2
Views
2K
Andris
  • Question
Android Question [SOLVED] B4A v13.0 BETA - error -> "The filename or extension is too long."
2 3
Replies
56
Views
15K
Daestrum
  • Locked
  • Question
Other B4A v13.0 BETA is available for download
2 3
Replies
42
Views
20K
Erel
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…