CSharpShellApp icon indicating copy to clipboard operation
CSharpShellApp copied to clipboard

APK Signing Problem

Open PeterKaa1 opened this issue 2 years ago • 7 comments

Hey man im trying to sign my apk through your app but it fails and says atleast one signer config must be provided but the problem is idk what it means because keystore and alias password is correct so pls help me

my device has android 10, 3GB ram

PeterKaa1 avatar May 17 '23 13:05 PeterKaa1

@PeterKaa1 As far I know that message only shows if a password is wrong. There appears to be a bug that always shows green when the window APK signing window is initially open. As a temporary workaround try retyping the passwords, they should both light up green.

radimitrov avatar May 17 '23 20:05 radimitrov

@PeterKaa1 As far I know that message only shows if a password is wrong. There appears to be a bug that always shows green when the window APK signing window is initially open. As a temporary workaround try retyping the passwords, they should both light up green.

I did that already multiple times and even reinstalled the app. You need to fix this bug.

PeterKaa1 avatar May 18 '23 13:05 PeterKaa1

@PeterKaa1 As far I know that message only shows if a password is wrong. There appears to be a bug that always shows green when the window APK signing window is initially open. As a temporary workaround try retyping the passwords, they should both light up green.

Using the exports apk app version btw

PeterKaa1 avatar May 18 '23 13:05 PeterKaa1

Found the problem. It is in Android <= 11. Both the keystore and alias password need to be the same due to system cryptography policies. I will release an update and bugfix for that non-Google Play version that applies this at keystore creation as well as extend the password error message.

radimitrov avatar May 19 '23 09:05 radimitrov

Found the problem. It is in Android <= 11. Both the keystore and alias password need to be the same due to system cryptography policies. I will release an update and bugfix for that non-Google Play version that applies this at keystore creation as well as extend the password error message.

Oh okay nice thank you, when do you think the non Google Play version update will be released and can you explain to me how you can fix that problem ?

PeterKaa1 avatar May 19 '23 11:05 PeterKaa1

No fix from what I'm reading beyond having a newer Android version. The only workaround seems to be alias and keystore password being the same. The update is going up soon however it only changes the keystore creation screen to apply the workaround.

radimitrov avatar May 19 '23 12:05 radimitrov

No fix from what I'm reading beyond having a newer Android version. The only workaround seems to be alias and keystore password being the same. The update is going up soon however it only changes the keystore creation screen to apply the workaround.

Can you add xapk export and mips abi support ?

PeterKaa1 avatar May 20 '23 16:05 PeterKaa1