-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Android Question targetSdkVersion="34" is it ready?
- Thread starter Scantech
- Start date
- Similar Threads Similar Threads
BTW, you can see the changes here: https://developer.android.com/about/versions/14/behavior-changes-all
And here: https://developer.android.com/about/versions/14/behavior-changes-14
I'm testing the changes.
You can test your app with targetSdkVersion=34 and report issues.
And here: https://developer.android.com/about/versions/14/behavior-changes-14
I'm testing the changes.
You can test your app with targetSdkVersion=34 and report issues.
Upvote
0
They ridiculously release new sdks constantly.
developer.android.com
Each time i boot up my Android studio i get gradle notification to update my sdk to the latest version, now its sdk 35 ?
SDK Platform release notes | Android Studio | Android Developers
Discover release information about the SDK packages available for download from the SDK Manager, in the SDK Platforms tab.
developer.android.com
Each time i boot up my Android studio i get gradle notification to update my sdk to the latest version, now its sdk 35 ?
Upvote
0
This is getting crazy !
Upvote
0
I received this warning within the Google play dashboard:
"Your app must target Android 14 (API level 34) or higher. Fix by August 30."
"Your app must target Android 14 (API level 34) or higher. Fix by August 30."
Upvote
0
You can set the targetsdk to higher version. But you need to test your app before publishing it to update in play store. @Erel Said already that he is testing the changes. And for sure will take care of it in any future release of b4a.
Refrence to migrate to higher targetsdk.
Background location tracking
Simple example of a foreground service that keeps the process running in the background. The current location is shown in the persistent notification. The app starts at boot and theoretically should run all the time. It also schedules itself to run with StartServiceAt. This can help in cases...
www.b4x.com
targetSdkVersion 34 foreground service for mediaPlayback
by following @Erel Update on this Post https://www.b4x.com/android/forum/threads/background-location-tracking.99873/#post-993226 targeting Sdkversion = 34, if you have a foregroundservice that do media play back in the background you will need to add this to your manifest in order to migrate...
www.b4x.com
Upvote
0
Thank you for the help. If I don’t update the app by August 30th, the app won’t be able to receive any more updates. ?
Thank you for the information. I’ll test it and get back to you!
Thank you for the information. I’ll test it and get back to you!
Upvote
0
Updated to 34 but still getting policy violations?
One of your test tracks may be targeting an old bundle that is still active. This is an interesting article about the issue and a possible "fix" (that is really not a fix, more of a work around).
Summary: You can replace old active bundles on your test tracks with "empty" bundles to get rid of the messages (or possibly a compliant bundle). Instructions are in the article. Do you want to do this? Googles recommendations are in the article. Basically, you can do this, but if you're not seeing a problem...don't worry about it. Yuck.
The potential problem? After Aug 30th, Can't update production track because an old "non-compliant" bundle is active in a test track. Can't update test track because (After August 30th) the app will be out of compliance, no updates will be allowed. So we won't know if there is a "problem" until after the 30th...and everything is locked up.
The comedy? In this article, Google says "...if you get stuck in that situation, just contact Google support and we'll help get it unstuck and resolve the situation..." LOL LOL Yaaaa righttttt.... I think i'll be uploading a "compliant" bundle to my test tracks before August 30th just to make sure.
Hope someone else reviews this article to make sure my assumptions are correct. Please correct or update if I have mis-understood what the article says.
One of your test tracks may be targeting an old bundle that is still active. This is an interesting article about the issue and a possible "fix" (that is really not a fix, more of a work around).
Summary: You can replace old active bundles on your test tracks with "empty" bundles to get rid of the messages (or possibly a compliant bundle). Instructions are in the article. Do you want to do this? Googles recommendations are in the article. Basically, you can do this, but if you're not seeing a problem...don't worry about it. Yuck.
The potential problem? After Aug 30th, Can't update production track because an old "non-compliant" bundle is active in a test track. Can't update test track because (After August 30th) the app will be out of compliance, no updates will be allowed. So we won't know if there is a "problem" until after the 30th...and everything is locked up.
The comedy? In this article, Google says "...if you get stuck in that situation, just contact Google support and we'll help get it unstuck and resolve the situation..." LOL LOL Yaaaa righttttt.... I think i'll be uploading a "compliant" bundle to my test tracks before August 30th just to make sure.
Hope someone else reviews this article to make sure my assumptions are correct. Please correct or update if I have mis-understood what the article says.
Upvote
0
edit: Oh, the beta is out!
B4A v13.0 BETA is available for download
I'm happy to release a new BETA version of B4A. The Android SDK and the underlying toolchain where updated with preparation for Android 14 (targetSdkVersion=34) requirements. Many of the internal libraries and also external libraries were updated and now depend on the latest Android SDK...
www.b4x.com
Last edited:
Upvote
0