Android Question Android 14 - API34 IDE Warnings

RichardN

Well-Known Member
Licensed User
Longtime User
To comply with Google's requirement to update to TargetSDKversion=34 by August I have recompliled my project with API34 and it seems to work entirely as expected. However the IDE continues to recommend not going higher than API 33.

Can I ignore this warning and upload the API 33 package? Am I risking problems with this store package or deployment to users?
 

Alex_197

Well-Known Member
Licensed User
Longtime User
To comply with Google's requirement to update to TargetSDKversion=34 by August I have recompliled my project with API34 and it seems to work entirely as expected. However the IDE continues to recommend not going higher than API 33.

Can I ignore this warning and upload the API 33 package? Am I risking problems with this store package or deployment to users?
It looks that the problem is on the Google Playmarket. It should be a waring but it looks like the error that prevents the app form punlishing.
 
Upvote 0

RichardN

Well-Known Member
Licensed User
Longtime User
@Alex_197

I am not sure I understand your (mis-spelt) answer. How is a log warning within the B4A IDE a problem with the Google Play store? I want to know if it is safe to distribute B4A APKs to the store when the IDE warns that TargetSDKversion should be 33 (and not 34).

I see there are problems with notifications in API34 but fortunately my package does not employ them so is it safe to publish?

Perhaps @Erel can clarify the situation?
 
Upvote 0

TILogistic

Expert
Licensed User
Longtime User
?
#IgnoreWarnings: 31, 34
see


1720258564307.png

1720258597193.png
 
Last edited:
Upvote 0

Alex_197

Well-Known Member
Licensed User
Longtime User
@Alex_197

I am not sure I understand your (mis-spelt) answer. How is a log warning within the B4A IDE a problem with the Google Play store? I want to know if it is safe to distribute B4A APKs to the store when the IDE warns that TargetSDKversion should be 33 (and not 34).

I see there are problems with notifications in API34 but fortunately my package does not employ them so is it safe to publish?

Perhaps @Erel can clarify the situation?
I don't think so you will be able to publish with API 33 due to Google playmarket error.

 
Upvote 0

NGUYEN TUAN ANH

Active Member
Licensed User
Ignore the warning. An updated version will be released in a few days and 34 will be the recommended targetSdkVersion.

For now the only issues (=things that actually require changes) I've seen are related to services.
Please let us know, specifically which services will be affected, thank you very much
 
Upvote 0

Alex_197

Well-Known Member
Licensed User
Longtime User
I updated my manifest to API 34 and tested it on my Android 14 phone.
I'm using FCM - so far so good. I don't even using Receiver, still using Services.
 
Upvote 0
Top