Failed to update Android app: Error from apksigner: ERROR (Jar signer CERT.RSA): Failed to parse JAR signature META-INF/CERT.RSA: java.security.cert.CertificateException: Failed to parse certificate #1

[TapirL]

Today, when I tried to update an apk for one of my app.

Google Play console apk upload page returns the following error:

Upload failed

You uploaded an APK with an invalid signature (learn more about signing).

Error from apksigner: ERROR (Jar signer CERT.RSA): Failed to parse JAR signature META-INF/CERT.RSA: java.security.cert.CertificateException: Failed to parse certificate #1

I can promise my certificate was never changed since it was created at the year 2011.

In recent three years, I really didn't use AIR SDK often.

But I remember that I really made a successful update for one of my apps.

Is there anything I missed in new AIR SDK versions?

Or is this a problem of Google Play?

BTW, three months ago, I transferred my apps to my another Google Play account.

Would this be the reason for the error?

Has anyone also encountered the same problem?

[marcanw]

Same here.

I uploaded an apk with exactly the same certificate and same air 29 one week ago and no problem.

Now it sends me the error mentioned in the op.

[s2472]

exactly same issue here one week ago was all sweet right now I'm getting following error

"

Upload failed

You uploaded an APK with an invalid signature (learn more about signing). Error from apksigner: ERROR (Jar signer CERT.RSA): Failed to parse JAR signature META-INF/CERT.RSA: java.security.cert.CertificateException: Failed to parse certificate #1"

[marcanw]

Damn after the apple review problem now it's android that refuses air apk...

[TapirL]

Got a reply from Google support:

I suspect that this is still related to the original bug, as it's not yet fixed but is being worked on. I think that whatever changes the engineers are making on the backend may be affecting the upload in this manner, but the issue should be resolved once they're finished.

Hope Google will fix it soon.

[andersemil]

Thank GOD I found this thread. I thought something had changed permanently in the way Google handles certificates. Please let us know as soon as you hear from Google support. TapirL​

[s2472]

I will be talking to google support about mentioned issue as soon as they are available so will post outcome here

[AlexFr69]

Same issue for us.

Last week it was impossible to access "edit release" on all tracks, now we can but when we try to upload an apk we have this error.

Our app is built with Air26.

[marcanw]

Got answer from Google:

Hi,

Thanks for contacting Google Play Developer Support to report the behavior you're seeing with getting the error message.

I’ve documented your issue and escalated it to our technical team for further investigation. Our team is working to resolve this issue for you as soon as possible.

I appreciate your patience and I’ll let you know the moment I have an update.

If you have any other questions in the meantime, please let me know.

Regards,
Rachel
Google Play Developer Support

Fingers crossed!

[marcanw]

I'm wondering whether Google is actively looking for a solution. Actually this issue seems to occur only on Air apk. So it might be a change on Google end that will not necessarily be fixed for Air package.

So maybe Air team should look into this and check with Google how to find a solution.

[andersemil]

marcanw​ I think TapirL​'s post with response from Google support gives us hope, at least they seem concerned... But ofcourse no idea how long it will take, since they may not have a clue why it stopped working yet.

[andersemil]

Apparently it's because Google Play Store has started rejecting APKs which are only signed with the V1 scheme (jarsigner - the old method) and now demand V2 scheme (apksigner - new method). Unfortunately, apksigner will not accept older certificates, AND you cannot change the certificate on an existing app, so we are screwed both ways. Google will have to relax their upload mechanism, otherwise many older apps will be unable to publish updates. Hope they do this soon as we have a very important update ready to publish.

[marcanw]

Indeed, I found this:

android - Upload new APK to Alpha - failed - Stack Overflow

I'm also very concerned I have to make a bug fix update asap.

[marcanw]

It might be a good idea to fill a bug tracker so Air Team is aware of the problem.

[marcanw]

Please vote:Tracker

[s2472]

guys please vote! although when I try to vote got msg "You can't vote for a bug you created" and I'm not the one who created the bug TapirL did

also noticed change of behaviour the the goole play now instead of throwing error when after uploading same .apk file the website seems like performing endless loop spin while processing...

[s2472]

so guys been able to succesfully add my apk file thank you google!!!

Your update to MobileHostViz, created on Apr 26, 2018, 2:57 PM, is live in the store.

yay!

[cgascons]

"I appreciate your patience while our team investigates the behavior you experienced. I checked in with our team and they’ve recently made some changes that should fix the problem. With the recent set of changes, please check to see if you’re still experiencing the same issue."

Fixed for us as well.

[AlexFr69]

Great news, i've been able to publish my app me too.

[andersemil]

Same here! Hooray. Somebody rolled some code back on the google server. Thank f*ck!

[marcanw]

Hourrah!