Closed Bug 988617 Opened 10 years ago Closed 10 years ago

Mozilla signed APK results in 'certificate expires too soon' error

Categories

(Marketplace Graveyard :: Integration, defect)

Product:
Marketplace Graveyard
Component:
Integration
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 988450

People

(Reporter: kumar, Unassigned)

Details

A user who tried to upload a Mozilla generated APK to Google Play got this error:

"You uploaded an APK signed with a certificate that expires too soon. You need to sign your APK with a certificate that expires farther into the future"

https://hacks.mozilla.org/2014/03/better-integration-for-open-web-apps-on-android/comment-page-1/#comment-2159228

The signer is currently setting expiration to 10 years which indeed seems to be a problem: 
http://developer.appcelerator.com/question/145979/upload-failure-to-google-play---signing-certificate-expires-to-soon-how-do-i-resolve-this
http://bugs.powerflasher.com/jira/browse/FDT-3229

According to the second link, we can set it to 30 years to bypass the error.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.