APK Signing Problem
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 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.
@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 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
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.
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 ?
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.
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 ?