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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to manage multiple ios google-service-plist while using react native ultimate config? #82

Open
MWaqasHussain-dev opened this issue Feb 3, 2022 · 4 comments
Labels
question Further information is requested

Comments

@MWaqasHussain-dev
Copy link

MWaqasHussain-dev commented Feb 3, 2022

I have handled the multi flavor part (Like DEV, STAG, PROD) for both android and ios ....

but i am stuck with with multiple google infoPlist file.... as i have three flavors so there would be 3 Plist file of firebase.....

How to manage and connect them when pre-action run or any other alternative for DEV, STAG, PROD.. Any idea
?

@MWaqasHussain-dev MWaqasHussain-dev added the question Further information is requested label Feb 3, 2022
@michalpazur
Copy link

What helped me is this great project. You can use .rnucrc.js file to copy files while changing the .env files. You can copy whatever you want, I use it to copy icons for different versions of the app as well as Firebase configuration files.

@aymkin
Copy link

aymkin commented Aug 24, 2022

@MWaqasHussain-dev pay attention to this file https://github.com/isilher/red-vs-blue/blob/master/.rnucrc.js

You can keep your different Google files somewhere in the project, let's say in folder white-label, and copy them to the ios or android folder during the env setup.

@dawidchyrzynski
Copy link

@quicksilverr
Copy link

Hye @aymkin @michalpazur But during add the base file, do we check copy items if needed and select create groups? Or just check copy reference?

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

No branches or pull requests

5 participants