// android signing
Android signing, explained simply.
Google needs every version of your app signed with the same key. This key is called your upload key. Push200 can create one for you, or use the one you already have.
No card needed. Expo, Capacitor, React Native and Flutter apps. Works with your existing GitHub repository. Your keys stay in your GitHub.
What an upload key is
An upload key is a small file with a password. Signing your app with it shows Google that the new version really comes from you. If a version is signed with a different key, Google Play refuses it.
Setting up your key
If your app is new
Press Create my Android key on your app's page. Download the file and save the password somewhere safe. This is the only time you'll see them, and we don't keep a copy.
If your app is already on Google Play
Choose Yes, it's already on Google Play and add the key you've used before, with its password. It usually ends in .jks, .keystore or .p12. If you can't find it, ask whoever published your app.
Where your key goes
Your key goes into your repository's encrypted GitHub secrets. Every Android build is signed with it and checked, then opened on a virtual phone and sent to Google Play as a draft.
If something goes wrong
I lost my Android key
Google can replace it. In Play Console, go to your app's App signing page and request an upload key reset. It takes a few days.
Google Play refused the upload
Usually this means the first upload hasn't been done by hand, or the key isn't the one Google expects for this app. Use the key you've used before.
Do you keep a copy of my Android key?
If we create a key for you, we don't keep a copy. You download the only copy, and your key goes into your encrypted GitHub secrets.
Your next release could be one click away.
Start free with no card. Set up your first app today.
Start free