Help Needed: Updating Target API Level to 34 for Google Play Compliance

[jesus77]

Hi everyone,

I hope you all are doing well.

I recently received a notification from Google Play stating that my app must target API level 34 or higher by August 31, 2024, to comply with their new requirements. Currently, my target SDK is set to API level 33.

Here is the message from Google Play (translated from spanish):

---

*Google Play requires that apps target API level 34 or higher.

Update your target API level by August 31, 2024, to publish updates to your app. We have detected that your app targets an older version of Android. To provide users with a secure experience, Google Play requires all apps to meet the target API level requirements.

As of August 31, 2024, if your target API level is more than one year old compared to the latest Android release, you will not be able to update your app.*

Could someone guide me through the process of updating the target API level in SAP Build Apps? Any detailed steps, documentation, or best practices would be greatly appreciated.

Thank you in advance for your help!

Best regards,

[Folidol]

Hi,

I also received the same message yesterday from Google Play.  Friends, please help.

Thqnk you...

[meagan1]

Hi, have you had any luck with this??? - I have the same issue...

[Folidol]

Hi,

I presume this issue would impact everyone who exported their Apps through Appgyver and published in Google Play Store. Hope SAP App Builder would address the issue quickly...thank you..

[aretesw]

same problem here

[VagnerSE]

I'm also having the same problem. I have been researching some solutions to update apk 33 to apk 34, I have been trying to use the apk tool program, but I have not been successful. I hope SAP can resolve this as soon as possible.

[gerardonet63]

The same error here. Did you manage to fix it??

[fairy]

same thing here :(( I've been stalking this thread for a couple weeks now but it doesn't look like there's been any updates from SAP themselves (T_T) I had this same issue last year for updating to android 13 and eventually they updated the build runtimes and it worked out but I recommend getting a deadline extension on the google play developer account to be safe! 

[ramg]

Hi all. Any news about this?

[fairy]

haven't seen anything yet )):

[Sololeveler]

Any update on this?

[fairy]

still nothing 🙃

[ramg]

In two days, will be impossible to publish Android apps....

[jesus77]

Hello! it seems that the issue is fixed, I have uploaded a new bundle and the target SDK is 34.

[fairy]

woohoo!! Thanks for the update :^D

[Sololeveler]

I was still rejected due to SDK not being 34, in the build section for my app it says: 4.11.167(latest)
Is this not the case for you? Is setting the SDK version somewhere else in the app?

[jesus77]

Hi, I don't know what might be the cause. I just created a new bundle (AAB) with the same runtime as yours and uploaded it to Google Play. The target SDK for me is 34.
It's true that my tests only consist of uploading the bundle. I haven't published any changes
Regards

[Sololeveler]

Thank you very much for your quick reply. So the SDK update did work, I was seeing the message for other build types like Internal testing, Closed testing etc. I found this link - https://stackoverflow.com/questions/50626453/cannot-remove-internal-test-track-build-from-google-pla... - on stackoverflow, if you go down to comment 13, you will see the fix i used to get rid of most of those SDK messages. Hope this helps. Thanks.

[ramg]

Great news!. But ... no official communication from SAP... This could be a bug, not a feature ...

[fairy]

this is how it worked out last year too :'')

[xyneodrew]

Had the same issue - what I did is applied an extension from Google Play store so that my current builds won't be affected and will have more time to wait for SAP team to fix and apply new sdk.