Hi @Omar,
Sure you’ve been waiting a month and it’s not easy to wait, but it has to be done. Again, we all understand your frustration, we’re all in the same boat, but it’s not a matter that’s the utmost concern. There’s always a possibility that when you awaken in the morning, it’ll be released!
Profoundly,
– 
Nathan
Are you seriously asking Kodular to release a buggy update?
If the bug is just appear when the app tries to save data in the device’s memory, I can avoid this easily by saving data in a real-time database as firebase and the app will work properly without any problems. I don’t ask Kodular to do something that they didn’t do before, they already did when they released Fenix. When Fenix has been released first time there were some bugs that affected just on few components although there is no alternatives for these components in Kodular but Kodular released Fenix with these bugs although releasing Fenix at this time wasn’t critical. But in our case, if the user don’t want to give you WRITE permissions you can easily tell him that he need always to be conneted to the internet to get the data stored in server side database.
Nice to catch up with you again @Omar,
Please stop talking about releasing the update, you’ve been going off-topic too much. This topic was originally created for Fenix and I suggest a moderator close it to prevent further confrontation.
Profoundly,
– Nathan
Ok, don’t be angry but you have to know that preventing people from writing their opinions in your community is not a solution because this will not change their opinions. Regards
Hello @Omar,
You can reply with all you want on the community, no one is stopping you, however you’re being relentless and it needs to stop at some point which is why I took the steps I did.
Profoundly,
– Nathan
The problem is that we don’t have one only word from the staff. It was said that everything was ready, they were just waiting for App Inventor to release it to update too. Now, a long time later, we still don’t have any explanation of why it didn’t happen or at least an expected release date. If I was told “there will be an update only in September or later” I would be more prepared for it. but no one expected it.
I think it costs absolutly nothing for Diego and others come here and say “hi people, we are busy working with Google Ad manager system or whatever, but we promise to introduce api 30 in the next xxxx days”.
I have found solution to this problem, but unfortunately, while I was uploading modified aab file, I received following message. Can anyone suggest solution?
“Your Android App Bundle has an invalid signature. Upload again with a valid signature.”
I have the same problem
Not sure but after modifying have you signed the aab ?
Read this guide
Hi @almeidapablo,
I want to first take the time and say that everyone here has a voice, and they are listened to. Your concerns, propositions, and questions continue to make Kodular more than it was before.
Continuing, there are a few flaws in your statements that I’d like to point out, that include responses to them.
“It was said that everything was ready, they were just waiting for App Inventor to release it to update too.”
I’m sure you’ve seen, however the new release from App Inventor has major flaws. It has a few issues. Staff won’t release something that has flaws, those that are public anyway.
“If I was told “there will be an update only in September or later” I would be more prepared for it. but no one expected it.”
The problem with this statement is that even if everyone had another timeline, there’d be complaints, mainly because people are growing impatient and think November starts tomorrow… It doesn’t.
“I think it costs absolutely nothing for Diego and others come here and say ‘hi people, we are busy working with Google Ad manager system or whatever, but we promise to introduce api 30 in the next x days.’”
At the end of July, staff were telling people the API 30 release would be out shortly after App Inventor released theirs. Dismally, this wasn’t the case. People were still complaining even when they had a coarse timeline, though this wasn’t the staffs fault, App Inventor hasn’t released their API 30 release at the time.
Thoughtfully,
– Nathan
One day!
Y’all will wake up and see the beautiful, bugfree KODULAR API 30 UPDATE,
Then all your frustrations will be gone and you shall have a biiiig smile on thine face!
Worry not Kodulars, for we await your perfection Kodular!
Hu ha ha ha ha haaaaa!!!
Absolutely, we are with Kodular team and we can wait 
after modifying ABB I was able to sign the Android.Keystore successfully, but I keep getting the same message
i am not sure why this is happening
See, since the output has already been signed, I did not find it compulsory.
I don’t know if decompiling and then recompile requires signature again.
Anyways, nice guess and I will use third party app signer and then again try uploading on console. If found successful, I will be releasing full tutorial, how to do it
I was able to sign and modify the SDK 30 of my application now the store is compatible with my application
This is the order of the tutorials I use to make it work.
1.- Edit or Modify the AAB file - #48 by Educacion_Virtual_Bolivia
2.- How to add asset and sign aab file
3.- Tutorial for signing an aab file
@Educacion_Virtual_Bolivia Playstore giving this error to me
Your Android App Bundle has an invalid signature. Upload again with a valid signature.
Follow these steps in the order that I indicate here, it worked for me now I can publish my to App
@CyberPunk
