Compile AAB manually

Guides
#1

As everyone knows and as expected, after the last update it is practically impossible to compile the AAB, having waited a month for the update and waiting another month to solve the problems, it is really a waste of money for those who make a monthly subscription.

Talk about kodular staff, lack of empathy, irresponsibility, bad service, etc. It doesn’t make sense because they are no longer interested in the project at all.
As already mentioned in the groups, after the implementation of Premium on an obsolete platform full of bugs, it caused a significant drop and total apathy among users. Well, that’s beside the point.

Just compile the APK, it already includes SDK 33, send it to the mobile along with our android.keystore file to convert it to AAB and be able to sign it.

image

On the mobile device we will need the APK to AAB Converter application that you can download from Google Play

image

open the APK to AAB Converter load the APK and convert it to AAB

  • It will ask us to see an advertisement to continue

image

After indicating the source APK and the destination AAB, we load our android.keystore.
In password we must put android.
Then we just click on BUILD AAB

image

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

We would already have our ABB with API 33

14 Likes
Can't build aab
Tomorrow is the last day of the deadline and so far there is no solution with the .abb applications
Export to aab or apk not working for any app
I download 3 programs( apk to aab converter)
Can't build aab
Can't build aab
Can't build aab
Can't build aab
Can't build aab
#2

Great work man, your guide will help us.

2 Likes
#3

This post was flagged by the community and is temporarily hidden.

#4

hello, where can I find the android.keystore file to manually convert the apk to aab

Can't build aab
#5

image

#6

I tried you method.

I tried to release the AAB to play store, getting below error while uploading in play store.

An error occurred while running bundletool build-apks on your uploaded App Bundle. Ensure that your App Bundle is valid by running bundletool build-apks locally and try again. Learn more. Error: Found multiple elements for key ‘com.google.android.gms.version’, expected at most one.

#7

Check the extensions used, it is not a problem related to the compilation

#8

https://community.kodular.io/search?context=topic&context_id=240115&q=com.google.android.gms.version&skip_context=true

Taifun

2 Likes
#9

This post was flagged by the community and is temporarily hidden.

#10

yes maybe still fix, they are probably working hard right now, they are professionals, you don’t need to be afraid, the time will come…now just wait ok

1 Like
#12

Great! it worked for me :relaxed:

1 Like
#13

3 posts were split to a new topic: How to compile aab offline

#14

Thank you so much, works fine and I already updated one of my apps on playstore.

1 Like
#15

Thanks Gaston, works for me when uploaded to Playstore!

1 Like
#16

Why google play still countdown 8days remain to fix sdk error ?

Screenshot_20231024_110638_Chrome
Screenshot_20231024_110638_Chrome1052×848 65 KB

1 Like
#17

I did all the steps correctly, but I always get this error
Can you help solve it urgently? I need an app update urgently before 10/27/2023 :slightly_frowning_face:

image
image473×920 67.9 KB

#18

Hey!
Thanks for the tool!
Unfortunately, after comleting the process te system tells me it couldn’t open the app when I try to install the newly-created .aab - do you have any idea why? I also need to update my app till the 31st… :frowning:

#19

and what is the console message? Have you already checked the extensions that are updated?

#20

Why you want to install the “abb” file? Just install the apk file from Kodular. The abb is only to upload in the playstore.

#21

my apk 20mb become 32 mb aab… is that normal?