Replies: 2 comments 1 reply
-
|
Hello @wesley-hl, As I shared in the email thread, you can refer to this Lost or compromised upload key |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
We have now found our keystore so require no more help with this. Thanks |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
If you are looking for help, please confirm the following...
Which mobile framework are you using?
Flutter (Dart)
Steps to reproduce
Hi, we have two workflows, one for our old Flutter codebase and another for our new Flutter codebase that supersedes the old one. They both need to publish Android builds to the same existing Play Store listing.
The Android keystore was originally added as an environment variable scoped to the old workflow. We now need to use the same keystore in the new workflow, but it doesn’t appear possible to reuse or promote workflow-scoped environment variables to the team level.
Unfortunately, we no longer have easy access to the original keystore file itself, and tracking it down across old machines and backups is proving time-consuming. The keystore already exists securely in Codemagic, so we’re hoping to reuse it rather than re-upload it.
To be clear, we’re not asking for the keystore to be exposed, downloaded or shared with us. We're only asking whether it’s possible for Codemagic to elevate or migrate the existing workflow-scoped keystore to a team-scoped/global level so it can be referenced by the new workflow.
Is this something you can help with please?
I am aware that you can request a new upload key but this is only if you have Google App Signing enabled on your play store listing, which we don't have enabled currently.
We would be willing to do whatever necessary to prove that we are the app and Codemagic account owners.
Expected results
The keystore currently scoped to a single workflow to be elevated to a team level secret.
Actual results
Currently the keystore is only available in the existing workflow and is not available for use in another workflow.
Build id (optional)
No response
Beta Was this translation helpful? Give feedback.
All reactions