AAB build stops after importing Android keystore created with Tarmus

[omarbagh]

Hello everyone,

I need help with a problem in MIT App Inventor.

I created an Android keystore using Talu (Termux/Talu tool), and I successfully imported it into MIT App Inventor. However, when I try to build the AAB (Android App Bundle), the build process starts but then stops and never finishes.

The keystore is accepted by App Inventor, but the AAB generation freezes during the build.

Has anyone experienced this problem before? Could the issue be related to the keystore format, the alias, the password, or the way the keystore was created with Talu?

Any help would be greatly appreciated. Thank you!

[Peter]

@omarbagh

The keystore is accepted by App Inventor, but the AAB generation freezes during the build.

Were you able to build the AAB before you used the keystore you generated?

[Boban]

Does your keystore contain this values, if not then it won't work.

Default Keystore Password - android
Default Keystore Alias - androidkey
Default Key Password - android

[omarbagh]

Thank you.

If the default values are required, could you please tell me how to create a keystore that is fully compatible with MIT App Inventor?

Should I use:

• Keystore password: android

• Alias: androidkey

• Key password: android

Is there anything else (keystore type, key algorithm, signature algorithm, or validity period) that must be set to specific values?

Thank you for your help.

I don't think I used the default values. I created the keystore in Termux using my own passwords and alias.

[omarbagh]

Hello,
Yes. Before using this keystore, I was able to generate the AAB file without any problems. The issue started after I began using the new keystore. MIT App Inventor accepts the keystore file, but the AAB generation gets stuck during compilation.
Thank you for your help.

[Anke]

@omarbagh

I created an Android keystore using Talu (Termux/Talu tool)

Why? And why don't you use the AI2 generated keystore?

[omarbagh]

Hello,

First of all, thank you very much for your time and for your willingness to help.

The keystore is created automatically when a new project is created. However, if the signing key is lost when releasing a new version, Google Play asks you to generate a new upload key using Android Studio or Termux.

Thank you.

[Anke]

@omarbagh

if the signing key is lost when releasing a new version, Google Play asks you to generate a new upload key using Android Studio or Termux

If your original keystore is lost—meaning you deleted it in AI2 for whatever reason—AI2 ​​creates a new one automatically. Of course, you can't use this to update an existing app in the Play Store. You have to ask Google to assign a new keystore to your app.

Creating a keystore with another tool doesn't change anything.

[omarbagh]

"Peace be upon you.

In fact, my Android keystore issue has been resolved. App Inventor accepted the key and successfully generated the AAB file, following the advice provided by Boban.

Thank you, sir, for your help. And thanks to everyone who contributed to this topic."