me neither.
1 Like
I have Same Problem any Solution??
Try this (temporarily):
- Take the last aia project of your app that you have successfully updated (published).
- Open it with Kodular and export the keystore and save it (android.keystore).
- Open the current project with Kodular you want to update and build the APK.
- Decompile this APK e.g. with AppToMarket.
- Import the saved keystore (android.keystore) into AppToMarket and rebuild (recompile) the APK.
- Sign and zipAlign the APK
- upload APK (“packageName”_new_zipAlign.apk) to the Play Store
That’s how I build all my apps (APKs) before I publish them in the Play Store (AI2, Kodular, AppyBuilder). The day before yesterday, I successfully released my last app (an AI2 projekt imported to Kodular) in the Play Store. AppToMarket (APK Studio, apktool or another tool) is also useful if you want to add larger files to a project or change something else.
Anke
2 Likes
Aia/project doesn’t contains any keystore it’s tied to your account.
Even though it has been speculated over this above, I have never managed to find a keystore in any aia file even though I have looked on 900+ projects
/Boban
Right, thanks for the hint, Boban. I downloaded my keystore when I created and published my first app and saved it locally. Since then I create almost all apps and releases with this keystore.
So if you have not saved the valid keystore, see here:
https://support.google.com/googleplay/android-developer/answer/7384423?hl=en
http://www.geekcodehub.com/2018/05/23/keystore-lost-in-android/
1 Like
Yes, always something to change, sorry but there is no builder out there that can do everything I want.
/Boban
I do not get what you want to say. A2M works fine for such purposes.
By “change something else” I mean, for example, customize the Manifest (remove some unnecessary permissions) or android:installLocation=“auto”.
I am Export aia for backup. If I export aia file then What changes in the Keystore.
Nothing 