We requested an upload-key reset. CI still signs with the old keystore and Play rejects the fingerprint. What is the safe cutover order?
Please wait
Opening question…
Fetching the latest questions and answers.
Fetching the latest questions and answers.
We requested an upload-key reset. CI still signs with the old keystore and Play rejects the fingerprint. What is the safe cutover order?
We requested an upload-key reset. CI still signs with the old keystore and Play rejects the fingerprint. What is the safe cutover order?
Wait for Play to accept the new upload certificate, then replace the CI secret and verify the fingerprint under App signing. Cut over on a closed-testing build first. Keep the old keystore offline for one more release cycle in case you must re-sign a hotfix that was already uploaded with the previous key.
No comments yet — start the conversation.