Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
/t5/air-discussions/apksigner-error-when-upload-playconsole/m-p/11331005#M56429
Aug 02, 2020
Aug 02, 2020
I can upload googleplay by changing targetSdk 30 to 29
for now
.
When I set targetSdk 30, I can not upload because
V2
Scheme sign needed.
To sign V2 Scheme,I need to use apksigner command.
But it is error.
When I create keystore,apksigner works.
So the error reason may be my p12,and it is 1024...
I wonder Using "
Google Play
App Signing" will be a solution of targetSdk 30.
In any case,I want to know whether it is impossible to upload googleplay by signing manually by use keystore(p12 1024) or not.
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
/t5/air-discussions/apksigner-error-when-upload-playconsole/m-p/11780645#M56794
Jan 25, 2021
Jan 25, 2021
Any updates on this issue ?
I didnt upload an update to my android app in a long time,
and now I am encountering this issuse.
I get this message from the Play Consol
Error from apksigner: ERROR: MIN_SIG_SCHEME_FOR_TARGET_SDK_NOT_MET: Target SDK version 33 requires a minimum of signature scheme v2.
Appreciate any lead on this
🙂
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more