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