Open JamesClent opened 10 months ago
@JamesClent might be best to set the title to something more precise like "Android 13 Required" for searchability purposes?
general cross-reference/discussion: https://forum.thegamecreators.com/thread/229280
I just wanted to add to this... It doesn't just affect uploading new apps. ALL of our existing apps will be removed from the Google Play Store if they don't comply by the end of August. We lose them all and the income they produce.
@neiltking Where have they said apps will be removed? I've only ready that no updates can be made without changing the target API.
@adambiser This was the email I got from Google Play Console:
Warning 17 of your apps are affected by Google Play's target API level requirements We've detected that 17 of your apps are targeting an old version of Android. To provide users with a safe and secure experience, Google Play requires all apps to meet target API level requirements before 31 Aug 2023. Action required Update the following apps to target the latest Android version ...
There is no mention of it only applying when I come to update the apps. When I click through to any of the apps (including one that was only published about a month ago using the newest AppGameKit Studio) it says:
App must target Android 13 (API level 33) or higher Fix by 31 Aug (11 days away)
So I am classing this as a requirement that needs immediate action.
Got that a few days ago, certainly makes android a bigger pain than it used to as this seems to happen on a yearly basis.
Same problem here
@neiltking The message I see is like it says in the first post.
In the Google Play console inbox:
From August 31, 2023, if your target API level is not within 1 year of the latest Android release, you won't be able to update your app.
On the details page for the message:
Status: You won't be able to release app updates (10 days away)
However, now I found this page, which explicitly says that they won't be delisted, just limited in availability until updated: https://support.google.com/googleplay/android-developer/answer/11926878
Starting August 31, 2023: ... Existing apps must target API level 31 or above to remain available to users on devices running Android OS higher than your app's target API level. Apps that target API level 30 or below (target API level 29 or below for Wear OS), will only be available on devices running Android OS same or lower than your apps’ target API level.
(I really hate having to dig around in 10 places in the documentation to find something only one of them says.)
We can request an extension to November 1st and hope TGC gets an update out sooner. If we target a higher API, it won't happen yearly.
Work will start on updating AGK to API 33 tomorrow. Expect to see a build in the next few days if all goes well.
@orvillian Thanks! I hope the update will be for Classic as well.
Awesome, thank you!
That's great news!
On Sun, Aug 20, 2023 at 10:59 AM orvillian @.***> wrote:
Work will start on updating AGK to API 33 tomorrow. Expect to see a build in the next few days if all goes well.
— Reply to this email directly, view it on GitHub https://github.com/TheGameCreators/AGK-Studio/issues/1114#issuecomment-1685318797, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM2MLRUL32P45P2WYK5IRRLXWIX6HANCNFSM6AAAAAA3WTL3LA . You are receiving this because you were mentioned.Message ID: @.***>
Wait a minute, I read that documentation page too quickly.
https://support.google.com/googleplay/android-developer/answer/11926878
Existing apps must target API level 31 or above to remain available to users on devices running Android OS higher than your app's target API level.
We currently target API 31, so we fall in this category. Unless Google forgot to update that part of the documentation, we won't have our app visibility limited. (We just can't update until we target 33.)
AAB export is broken on the latest release so I'm assuming that this will have to be fixed at the same time as updating the API to 33?
Zaxxan, is AAB export broken on both Classic and Studio?
The AAB export issue has been fixed and everything now targets API 33. I have been able to export and upload an AAB and everything looked fine in the Google Play Console. More tests required tomorrow and then I expect the Studio update to be released on Wednesday.
Thank you, orvillian. We really need to use Classic because Studio produces slower-running apps; we have found from experience that the created apps run too slowly resulting in poor performance on some Android devices.
@SuperiorInteractive I may be able to update Classic but on Windows only. There's probably not enough time to sort it this week or next so if possible at the very earliest it would be looked at from 4th September. In the meantime you can request more time for your apps. I have tested this with some and the deadline was immediately extended to November.
@orvillian thanks for the update and thanks for continuing to update the classic windows version.
@orvillian Thanks for the update :) I own both Classic and Studio, but I usually compile with Classic, so I've just requested time extensions for my apps, which have been approved.
Also, I just compiled a Windows executable with Classic, and the time stamp is always 30/01/2023 22:17 That's not big a deal as I can easily change the time stamp, but maybe it can be fixed during the Classic API 33 update.
Cheers
@Psy-Labs The Windows executable doesn't get compiled, the bytecode does. The EXE is just copied from the AGK folder.
@orvillian Thank you. The time extensions for our apps have been approved. We would certainly be very appreciative if you could update Classic for Windows only.
@adambiser Thanks for the info, makes sense. The Studio version sets the time stamp right, though. The .exe always has the same time stamp as the bytecode
@Psy-Labs Ah, I wasn't aware that Studio did differently.
I have published four apps today with and without adverts and all is working well. In the event you use adverts you will need to tick the new permission for the advertising ID in the export dialog. You will also need to update your data safety declaration form inside the Play Console..
Not much left to do and then a Windows update will be available through TGC and Steam tomorrow. All being well a Mac version will also be released.
Thanks @orvillian ! Is there a way to disable AD_ID so that our apps with ads can be in the Google Play Family program?
@adambiser Yes, just make sure the advertising permission box is not checked when you export.
@orvillian OK. I know AD_ID isn't what this is about here, but I'll also point out [https://github.com/TheGameCreators/AGK-Studio/issues/1052#issuecomment-1507708674](this AD_ID-related comment). Does classes.dex still declare the AD_ID permission? If so, we might be getting that permission set even without requesting it explicitly.
And the crappy thing is, Google accepts updates for this fine, but tell you later that they violate the Family program policy and will be removed. I finally had to remove my apps from the Family program.
I'll wait and see. Thanks for your work on this!
@adambiser I did a test with an app that used adverts and didn't declare the AD_ID to see what happened and got an error when uploading to the play console saying I needed to add it. I can't see it being used anywhere else so I'm hopeful it's sorted.
@orvillian Thanks again.
AGK Studio update for Windows is live on Steam and TGC. The only change has been to handle the new API requirements from Google.
I've just downloaded the TGC version and it doesn't appear to have been signed correctly. Windows detects the publish as unknown.
@Zaxxan This is what I see for it -
I'll look into it.
I get the 'windows protected your pc' message and when I click on more info it says publisher: unknown publisher
@Zaxxan Fixed. New installer is up.
Ok thank you. I have just tried the new TGC version and it installs ok and exports AAB files ok. So far so good 😊
Thank you for the update and quick fix
(I did have problem with the jarsigner but it was due to a corrupt java installation)
added Classic tag as i believe this issue is now only apparent for Classic
Just to confirm: I rebuilt the "aab" package file for one of my apps using the newest version of AppGameKit Studio (2023.08.23a) with no problems and submitted it to the Google Play Store as a test. The target SDK version shows as "33" for me when Google analyses the package. I can confirm that it was accepted with no problems, and after a couple of days the new version of the app is now available in the store. The warning in Google Play Console about the app not adhering to Google Play Developer Programme Policies has gone. Looking good. Now to rebuild all the other apps and submit them :) Thanks @orvillian
How come my dropdown doesn't show SDK 33? Only goes to 12 (31)???
On Tue, Aug 29, 2023 at 6:10 AM neiltking @.***> wrote:
Just to confirm: I rebuilt the "aab" package file for one of my apps using the newest version of AppGameKit Studio (2023.08.23a) with no problems and submitted it to the Google Play Store as a test. The target SDK version shows as "33" for me when Google analyses the package. I can confirm that it was accepted with no problems, and after a couple of days the new version of the app is now available in the store. The warning in Google Play Console about the app not adhering to Google Play Developer Programme Policies has gone. Looking good. Now to rebuild all the other apps and submit them :) Thanks @orvillian https://github.com/orvillian
— Reply to this email directly, view it on GitHub https://github.com/TheGameCreators/AGK-Studio/issues/1114#issuecomment-1697236001, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM2MLRTASDOAXWX3CADCABDXXXEXFANCNFSM6AAAAAA3WTL3LA . You are receiving this because you were mentioned.Message ID: @.***>
Will there be an update for Classic addressing this? Thanks.
@orvillian Have you had any chance to look at updating the Classic version? As mentioned, we need the Classic version for our apps, so I would be very appreciative if you can put out an updated Classic version for Windows, please.
A Windows update will be sorted out in the next couple of weeks.
The dropdown only lists the minimum API. While it does need updating behind the scenes the target API is set to 33 to comply with the new policies.
@orvillian Thank you. 👍🏻
Any news on the Classic update? The Google Play API Deadline is only 10 days away...
I'll find out what's going on. I know there is an update planned, but could have been delayed, due to future AGK plans. Sorry to be vague, but my main focus is MAX these days, and I wouldn't want to misinform you guys.
I'll find out what's going on. I know there is an update planned, but could have been delayed, due to future AGK plans. Sorry to be vague, but my main focus is MAX these days, and I wouldn't want to misinform you guys.
Thank you. This is becoming rather urgent now, please.
Thank you Dave :)
Hi everyone. I've spoken to Lee and he's confirmed that the new version supporting the latest version of Andriod, along with a larger announcement about AGK and it's future direction, will be released this week.
Testing the new AGK Classic build now -
A new option has been added into the export to deal with the advertising ID -
Expect a build in the next few hours.
Woot...good news :) Thanks Dave and Orvillian !!
11 days from now I cannot submit APPS anymore, since you don't support Android 13 for compilation. This is a high priority item for me. After waiting for the iOS fix, not I have to wait for an Android fix.