Bad Password or Key File ( I cant build any APK )

[jozhua zelwyn]

I tried everything, reinstalled, DroidScript. Reinstalled APK Builder Plugin, my package name is correct and acceptable, my newly created user.keystore uses the correct password when building. But still the error occurs, "Bad Password or Key File."

I never uploaded an apk to playstore, in fact I cant even build one to start with.

I need solutions.. Ive been so frustrated Im doing everything I can.

[Dave]

You must have got your password wrong but if you have never uploaded to the PlayStore then you are safe to delete or rename your keystore file.

You can find it in your Internal Storage/DroidScript/APKs folder, it's called user.keystore.

I suggest you rename it to user.keystore.old and then restart DS

[Kallikratidas]

Can I ask something? If you remove the debug.keystore file, can you make it again the same be entering the Same organization name, name and password?

[Steve Garman]

The debug.keystore file is always created the same and is not signed.

I'm sure you are thinking of user.keystore

I'm almost sure that if you create a new user.keystore file with the old details it will not be recognised as the same signature.

[Steve Garman]

As a test, I just created 2 new user.keystore files using identical details.

The two files are noticeably different

[Kallikratidas]

Alright Steve,
Thanks for the information!
So, that means that rather it is created using some random or time parameters or worse, that we can not make a copy. But I think, that we are allowed to make copies of the file. I don't understand much why it is created under some randomness, maybe for security, but that means that we have to store it and make many copies...!

[Steve Garman]

From day one when the apkbuilder plugin went into beta, when you create a keystore file, the following message has always been displayed

WARNING
A 'user.keystore' file has now been created in the DroidScript/APKs folder.

It is STRONGLY recomended that you backup this file. You cannot update Google Play Apps released using this key, unless you have the original file (and can also remember the password!)

Note: If you rename or delete this file, you will be asked to create a new one again.

[Kallikratidas]

Basically, I just found out, that even if you loose it, you may be able to reset it.
https://stackoverflow.com/questions/47613498/lost-keystore-file-for-app-but-have-google-play-app-signing-enabled

Anyway, thanks for reminding this message Steve. I always use the debug build, because it didn't happen that I upload an apk in GooglePlay till now.

Regards

[Fatih Elitas]

If the source of this problem is your image files and special characters such as Turkish, the "ş, ğ, İ" apk is not created. gives bad password error.

[Steve Garman]

@Kallikratidas,
The Stackoverflow solution you posted is only applicable to apps signed online with Google App Signing.

APKs built with DroidScript are not compatible with Google App Signing so Google will not be able to help if you lose your keystore file.

The ONLY way to ensure you can update a DS app on Google Play is to ensure you always have access to a copy of the user.keystore file with which it was originally signed.

Please do not dilute the message about making sure you keep safe backups. It is the only way to ensure you can continue to update your app on Google Play.

[Kallikratidas]

Alright, I am sorry for this misinformation. I didn't know this detail. I thought it had to do with the account you are using in google play. Not the android studio or whatever else. Anyway, thanks for making it clear to me.

Regards!