Change API level to 33 (Manually Compile AAB)

[Shalom_Cephas]

@Gaston

just compile the APK as usual

Now it will be necessary to have the program (APK Easy Tool 1.6) comes in a portable version

once downloaded, in my case, the directory creates a folder called APK to have the file that I just compiled.

then we execute the apkeasytool and we go to browse > we select the APK and click on Decompile

when finished, at the bottom we can see what it says (SDK 31) we open the decompile directory

API: With any text editor we open the apktool.yml file and change the value to 33

now we compile the APK you can already see that the SDK increased to 33, send it to the mobile along with our android.keystore file to convert it to AAB and be able to sign it

on the mobile device we will need 2 apps APKtoAAB and Zipsigner

open the APKtoAAB load the APK and convert it to AAB

We open the ZipSigner and look for the directory where our AAB is

Then we go to the 3 dots and select My Keys > Register keystore

we select our android.keystore and it will ask us for a password, we place (android)

in Key/mode we select androidkey and give the button Sign the file.

We wait for the process to finish and that will be all.

We would already have our ABB with

Where to Download these sofweres?

[Taifun]

@Shalom_Cephas

Where to Download these sofweres

what about doing a Google search?
btw. the wiser option would be to just wait or in case you have to update your app now, extend the deadline until November as described here

API Level 33 Necessary from August 2023

Taifun

[Nicolas (4xnico)]

Hello, help needed:
How do I get android.keystore file for ZipSigner? Thanks.

[Duy_Ph_m1 (Duy Phạm)]

Go to Account → Preferences, at the General tab, you’ll see the Keystore section and Export keystore button.

[lunatic_droid]

And me again.
I tried this with several of my apps on different laptops/notebooks and I always get when I upload the signed apk to google play store: “MIN_SIG_SCHEME_FOR_TARGET_SDK_NOT_MET: Target SDK version 33 requires a minimum of signature scheme v2; the APK is not signed with this or a later signature scheme.”
I have ZipSigner version 3.4.
Strange that no one else encountered this problem …

[lunatic_droid]

Now, I think I found my problem.
I tried the guide without the apk-to-aab-conversion.
I wanted to maintain my apk version and loaded them up to the play store and that causes the error messages.
Now, I converted one of my apks to aab and loaded it up and all is fine.
I will try it with my other apps.
This is a very good guide and my rescue.
Thank you very much.

[malik2 (malik jamaludin)]

try this step, it’s very easy to convert (solution), but it’s better to wait for kodular update to targetdk 33, maybe in september/october

How to change Target SDK version 30 to 31 in Kodular apps

[Caution_Tuner]

Follow This

Help! , how to get to SDK API TARGET 33 ( Android 13 )

try this step, it’s very easy to convert (solution), but better yet wait for kodular update to targetsdk 33, maybe in september/october [How to change Target SDK version 30 to 31 in Kodular apps]

[Iksan_Arisandi]

(post deleted by author)

[Thembani_Dlamini]

does google play accept this, has anyone tried it ?

[Taifun]

Yes, you can do that… however there are also the behavioral changes to consider…
See also

API 31 to 33 Update Service

you are already posting it… and here is my opinion about such service (as already said in other threads) it does not really make sense to target sdk33 manually, because also the behavioral changes must be implemented, see also this thread Permissions with new Target API 33 - #2 by Taifun The best strategy imho therefore is to extend the deadline as explained here API Level 33 Necessary from August 2023 - #22 by The_K_Studio - MIT App Inventor Help - MIT App Inventor Community and build your…

Taifun

[Angel_Betancourt]

thank you I really needed this

[AIC_AIColon]

What a shame, it’s time to update the API to 33. Following these steps, it only allows it to be accepted by Google Play but contains errors when converting it to the .aab format, for example the error 703

,when it could not find the MP3 file.

[Gaston (zodiaclogic)]

Friend, check your blocks, you are doing something wrong, your error has nothing to do with the topic, in fact I just updated an app with mp3 sounds and I didn’t have any problems

[Taifun]

You are trying to play a mp3 file… starting with SDK33 you have to ask for audio permission… this is one of those behavioral changes I mentioned earlier…

therefore if you have an update for an already existing app the wiser method is to extend the deadline and to upload using the old SDK31 until Kodular provides the SDK33 update including all behavioral changes

Taifun

[i_code]

Can u plz say when the up date will be ready ???

[AIC_AIColon]

Dear friends. Thank you for wanting to help but I found the problem was not in my code, but in the apk to aab converter, please do not use it anymore. Use the Aabinstaller app, it will not generate any errors.

[Developer_Micheal]

I follow the tutorial but app did not decompile, it just show decompiling…

And nothing happen til 4 hours, the locate compiled apk button not active to click

[Shalom_Cephas]

We are adviced To be patient until Kodular Release SDK33
Extend the deadline.
Hope Kodular are Working on this if not they couldnot ask for our patient
Thank you

[rahmatdoank1 (bangmamettt)]

you can create with Kodular, export AIA project, import AIA with MIT APP Inventor, build aab from MIT App inventor

i just did this while kodular update sdk33