After building our app a few times we realized we were using our internal build name
burgertime for the slug in the
After changing it to the real app name,
awesome, it appears Expo issued a new security certificate and now the Play Store won’t accept the .apk file.
Here’s what our build history looks like.
Here is what the
View Logs has for a slug on red build.
And here it is for the blue build.
Is there any way to sync the keystore back to the one generated during the
burgertime slug build?
We have the Play Store entry, bundleIdentifier, and testers all set up on that slug. It would suck to have to do it all over again; forcing a changing our identifier which is what the Play Store says you must do if your certificates change.
Or, is something else wrong here? Maybe I misdiagnosed the problem.
Thanks you for any help!!
Hi @gollyjer - if you change your app slug back to the old one, you should then be able to fetch your old keystore from our servers by running
exp fetch:android:keystore. Then, the next time you make a build with your new slug, just upload your old keystore (by using the
exp build:android --keystore-path option). Hope this helps – sorry for the inconvenience!
Should I do a build before fetching the keystore, or is simply changing the slug enough?
Never mind. Simply changing the slug was enough. Thanks!!
For anyone reading along.
I changed the slug in app.json and ran
This downloaded the
.jks file and printed the following to the console.
Then I ran
exp build:android --clear-credentials
This presented me with the option to choose
- Have Expo manage my keys.
- Upload my own key.
I chose #2, input the file location, and typed the Key Alias, Password, and Keystore Password.
After it finished I downloaded the .apk, uploaded to the store… and we’re in business!!
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.