Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to automate expo upload:android #68

Open
dmiranda2791 opened this issue Oct 23, 2020 · 4 comments
Open

How to automate expo upload:android #68

dmiranda2791 opened this issue Oct 23, 2020 · 4 comments

Comments

@dmiranda2791
Copy link

dmiranda2791 commented Oct 23, 2020

Hello! It's me again 馃槃

Topic and scope of discussion

How would you pass service account JSON to expo upload:android?

Motivation

I want to create a manually triggered Github action to automate uploads to Play Store?

Additional context

expo upload:android requires the --path to the JSON file containing the service account. I dug into the expo-cli code and they use fs.readFile to get the content so not sure how to make it available inside the Github actions. Do you know a way to provide it?

@byCedric
Copy link
Member

Hi @dmiranda2791! Having "secret files" instead of "secret env vars" is a bit harder, but not impossible 馃槃 You are lucky that the Google Service file is a JSON file, meaning you can easily serialize and deserialize to and from a string. I would recommend putting the contents of your Google Service file into a secret envvar, and use this to convert it to a file.

After that, you can simply point to your newly created file and continue the process. Let me know if that works for you!

@dmiranda2791
Copy link
Author

Thanks! I'll give it a try 馃榿

I'll told you how it goes

@dmiranda2791
Copy link
Author

Thank you @byCedric! It worked perfectly, I have automated uploads Play Store now 馃榿

@byCedric
Copy link
Member

Awesome, I'll keep this issue open to add it as an example!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants