- Jun 6, 2020
- 11,559
- 4,422
I created a new app and uploaded it to Google Play by creating a new private signing key suitable for a bundle.
I then tried to update an old app and had to delete it from my device to be able to install it with the new key.
When I try to upload that to Google Play it refuses it because b4a now uses the new key.
Tried wth the old key still refused.
Followed the extract instructions Google now give using the pep file but when I uploaded the extract I got: The private key was not properly encrypted, or is not a type of key we support
(btw the ajava version used by b4a (1.8) didn't work, had to go to sdk19.)
The instructions in post 91703 are confusing because it don't specify what parts of the commands should be replaced with own specific files and keys and what is the same for all keystores created using b4a.
Is there a newer post with instructions for what to do with Google Play as it is now after the option of signing the old way has gone and b4a now has a Build App Bundle menu...
I then tried to update an old app and had to delete it from my device to be able to install it with the new key.
When I try to upload that to Google Play it refuses it because b4a now uses the new key.
Tried wth the old key still refused.
Followed the extract instructions Google now give using the pep file but when I uploaded the extract I got: The private key was not properly encrypted, or is not a type of key we support
(btw the ajava version used by b4a (1.8) didn't work, had to go to sdk19.)
The instructions in post 91703 are confusing because it don't specify what parts of the commands should be replaced with own specific files and keys and what is the same for all keystores created using b4a.
Is there a newer post with instructions for what to do with Google Play as it is now after the option of signing the old way has gone and b4a now has a Build App Bundle menu...
برای دیدن لینک ها باید ثبت نام کنید
برای دیدن لینک ها باید ثبت نام کنید