Our app, used to work. The last update published 2 and a half weeks ago when the apk file created and worked properly.
The last 2 days when we are trying to create
I had a similar issue before while releasing apk, i was not able to install it, that was happening if the signature v2 is checked.
Unfortunately, I am not really sure why it causes such problems! anyway if you checked v2 try to uncheck it and use only v1 (the jar signature).
Also thanks to @codeMagic for providing us with this STO thread about differences between both types.
I fixed that the same which mentioned above, by applying v1 signing only and turn off v2 signing, moreover that can be done through gradle
build file by settings value for v1SigningEnabled
& v2SigningEnabled
as the following:
signingConfigs {
staging {
keyAlias *****
keyPassword *****
storeFile file(*****)
storePassword *****
v1SigningEnabled true
v2SigningEnabled false
}
release {
keyAlias *****
keyPassword *****
storeFile file(*****)
storePassword *****
v1SigningEnabled true
v2SigningEnabled false
}
}