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 do I set the google api key from react native side? #166

Closed
anil1712 opened this issue Aug 8, 2018 · 2 comments
Closed

How do I set the google api key from react native side? #166

anil1712 opened this issue Aug 8, 2018 · 2 comments

Comments

@anil1712
Copy link

anil1712 commented Aug 8, 2018

Hi,

I don't want to set the default API key always in my app, it should be configurable. Is there any possibility of existing implementation?

The scenario will be something like this,

  • After launching the app there will be a login screen.
  • In login success response, react native client will get the Google API key, so on that time, I want to set the API key.

So let me know if there any solution for this scenario.

Thanks,
Anil

@devlinb
Copy link

devlinb commented Nov 1, 2018

Google allows you to generate an API key that can only be used by a given app bundle. Use that, and the other security options offered by Google, to safeguard your API key.

What you are proposing won't help any, anyone who wants to take your key can do so once it is transferred to the phone.

In regards to security, if it is on the device, the user has access to it, it is after all their device!

(DRM schemes for secure video playback aside)

@tolu360
Copy link
Owner

tolu360 commented Mar 11, 2019

@anil1712 Please update to the latest release, comes with extra steps to protect your keys. @devlinb is right, what you propose would not be helpful in the light of new billing system by Google. Please see #198

@tolu360 tolu360 closed this as completed Mar 11, 2019
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

3 participants