an off-branch version of Classic for WIN (only) was posted a couple of days ago meant to meet google play's api33 requirement effective nov. 1st (with the extension).

while orvillion's been able to export without issues, others have not receiving "failed to read manifest file when exporting to aab" errors referencing a missing "build_bundle" folder.

this api33 version of Classic is only meant to address the GP requirement and is not part of the main Classic branch @ steam.

if you're not familiar with installing others versions @ steam, see HERE and look for the api33 version.

i believe similar is available for the TGC version @ your products list (don't quote me; i don't own the TGC version).

if you don't need the api33 exports, i would stick to the current "main" branch of Classic (or switch back to it when finished with exporting). ie, v2023.01.26.

@ steam, you'd choose the "none" option under the betas pull-down to revert (as i understand it, that's what the "api33 backup" version you'll see is, as well, but i expect that's "off branch").

This method worked for me but you need to own the Studio version as well:-

Delete or rename the data\android folder from the October update and replace it with the android folder from the August Studio version and this then produces a AAB using android33.jar

For example:

First delete or rename C:\program files(x86)\the game creators\agk2\tier 1\editor\data\android

Obviously make a backup before deleting!

Replace with C\program files(x86)\the game creators\appgamekit studio\media\data\android

I have successfully created both APK and AAB exports @ API level 33 and uploaded the AAB to play store. The apps run as expected with no crashing etc.

Thank you, Zaxxan!

Your suggested procedure has worked and the apps have been successfully exported and updated in AAB format.

So you need Studio to fix this in Classic. Way to go.

I know it's not ideal but it's a work around for people who need to update their apps before the Google deadline as Orvillian has said on GitHub that this issue is unlikely to be fixed in time.

If TGC could provide the android folder in a zip file then you wouldn't need studio. This update was only released so that users could update to API 33, if you don't need API 33 then the recommendation is to stay on the January update.

I totally forgot to test my apps after updating
None of them is working anymore. They shut down immediately after being started...

Is this using the spamming method or swapping the android folder? So far I haven't had any issues.

This is using the spamming / USB method.
I just compiled a new version after swapping the Android folder like you said and uploaded it.
It's in review now. I'll let you know ASAP.

The app I uploaded has passed the review stage ok. So fingers crossed.

All apps have been approved
Thanks alot for the solution!!

@orvillian, I have narrowed this issue down further.

It appears that there are files missing from the C:\Program Files (x86)\The Game Creators\AGK2_old\Tier 1\Editor\data\android\sourceGoogle\resMerged folder.

If I copy a file called mipmap-anydpi-v26_ic_launcher.xml.flat from the Studio resMerged folder to the Classic resMerged folder the export then works OK.

The are several mipmap files missing but the above file seems to cause the issue we are seeing. It would be helpful if someone else could confirm this.

It's also possible to fix the html export by copying the C:\Program Files (x86)\The Game Creators\AGK2\Tier 1\Editor\data\html5 folder from the January update as there are a lot of files missing from the October html5 folder.

I think I now have a fully functioning version.

@zaxxan,

so, your last post fixes export on its own/without studio?

I think I now have a fully functioning version.

let me know so i can mark the correct post as the solution.

meanwhile, thanks for working on this.

To fix the android AAB export you still need the mipmap-anydpi-v26_ic_launcher.xml.flat file from Studio.

To fix the html5 export you need the January version of Classic for the missing html5 files.

I'm hoping that now I've found the cause of the issues that Orvillian will release a new update with the fixes.

I get failed to read manifest file at C...(some more stuff)
After trying to export after updating to the beta for api33

Can someone send me that file of studio I cannot afford to buy it

PLEASE HELP

Can someone send me that file of studio

i'm asking for permission to post the required files. as it's the weekend, i wouldn't expect a response soon. until then, sorry.

meanwhile, please don't multi-post or spam (here or steam), @kocak. i know it's getting crunch time but it's not gonna speed things up.

I have some good news, the mipmap-anydpi-v26_ic_launcher.xml.flat exists in the January version of Classic so you don't need studio to fix the aab export issue.

so....

To fix the android AAB export you need to copy the mipmap-anydpi-v26_ic_launcher.xml.flat file from the resMerge folder in the January 2023 update (there are other missing mipmap files so it may be just as well to copy these over from the January 2023 to the OCtober 2023 version as well)

To fix the html5 export you need the January version of Classic for the missing html5 files.

I'm hoping that now I've found the cause of the issues that Orvillian will release a new update with the fixes.

I have some good news, the mipmap-anydpi-v26_ic_launcher.xml.flat exists in the January version of Classic so you don't need Studio to fix the AAB export issue.

so....

To fix the android AAB export you need to copy the mipmap-anydpi-v26_ic_launcher.xml.flat file from the resMerge folder in the January 2023 update (there are other missing mipmap files so it may be just as well to copy these over from the January 2023 to the October 2023 version as well)

Path: C:\Program Files (x86)\The Game Creators\AGK2\Tier 1\Editor\data\android\sourceGoogle\resMerged

To fix the html5 export you need the January version of Classic for the missing html5 files.

Path: C:\Program Files (x86)\The Game Creators\AGK2\Tier 1\Editor\data\html5

I'm hoping that now I've found the cause of the issues (which is basically lots of files missing) that Orvillian will release a new update with the fixes.

Update: user @weave had to copy ALL of the missing mipmap files to successfully export a AAB file. So I recommend doing this now to make the fix more likely to succeed.

@zaxxan,

and, gp accepts the export and the app runs fine with the files carried over from previous version, correct?

Yes, they have for me. It would be nice if someone else could test it as well though. I have exported apk, aab and html5.

I've copied the Android Studio folder to the Classic installation, exported 3 apps to .aab and uploaded them to Google Play.
They have been accepted and run just fine