Okay Peter
Yes, both APKs have the same keystore. So it should work to update your app in the Play Store. I have probably done this more than 1000 times and have never had a problem with it.
1 Like
If they have the same keystore, then why is it when I upload I get that error?
But wait, can you check if this has the same keystore;
39.apk (9.4 MB)
The same, should work.
Should I upload you a screen record of me uploading, because its still bringing the same error.
And that’s why I would like @Pete to tag @Kodular
This has nothing to do with Kodular.
2 Likes
Now Kindly advise on what I should do
Yes, do that and be sure that you upload the same APK as you sent to me.
It is best to show the entire upload process until the error message.
1 Like
Yes, I’m not sure what’s going on. It seems to be related to the fact that you have activated this:
(I also used that in some of my apps and never had any problems.)
Let’s simplify that, try the following:
1 Like
Since you enrolled in app signing by Google Play, you have to use upload certificate key, which one is that, did you get any from google etc
1 Like
This request is 4 days old, so what did you upload to google or where is that key?
Nothing so far,I contacted Google Support team and the told me to upload a .PEM folder, however I followed a link you gave to do so but am unable. Not familiar with CMD
No key
Currently, there are three keys present
-
key that google is signing your app with
-
your file 36 and 39 contains 1 key that also was used as upload key and thereby worked before
-
at some point you did something as per your request you have a new upload key that you also have to confirm with a pem file
how and what you did I can’t say
1 Like
Why don’t you tell us this first?
Instead, we’re puzzling around here unnecessarily.
See here: