-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shorebird preview
calls bundle-tool build-apks
which might sign with the wrong keystore
#2113
Comments
I realise this error is because |
I would expect There might still be something for us to fix here? I'm not yet sure. |
So I checked the certificate of the aab file and it WAS the correct (release) one. But the preview command was still using debug.keystore according to it's logs. It looks like the preview command builds the apks using I think this issue was just because I changed my default debug keystore in build.gradle for a reason which wasn't actually a good reason, and probably nobody ever needs to change it |
Wow, you're right. I didn't realize that bundletool could end up changing the signing!
|
shorebird preview
calls bundle-tool build-apks
which might sign with the wrong keystore
App ID: 71b9cd57-235e-40ab-8d25-1861aa29aadf
Description
I am getting the following error after creating an android release and then running
shorebird preview
. Changed my keystore for the release version after setting up shorebird, but looking at the logs (The APKs will be signed with the debug keystore found at '/home/john/.android/debug.keystore'.
), it is still trying to use the old keystore (debug.keystore
).I've tried reinstalling shorebird, cleaning cache, re-initialising shorebird and cleaning flutter cache.
Error:
Steps To Reproduce
Expected Behavior
Shorebird should use the new keystore
The text was updated successfully, but these errors were encountered: