Skip to content

Fix leak off api key by loading from manifest xml#256

Open
diegojimenes wants to merge 6 commits intotolu360:masterfrom
diegojimenes:fix-leak-off-api-key-by-loading-from-manifest-xml
Open

Fix leak off api key by loading from manifest xml#256
diegojimenes wants to merge 6 commits intotolu360:masterfrom
diegojimenes:fix-leak-off-api-key-by-loading-from-manifest-xml

Conversation

@diegojimenes
Copy link

i had a little problem with play store because the key of google places was be exposed in the gradle properties, so i move it to android manifest. but i don't know if is a correct approach.

@tolu360
Copy link
Owner

tolu360 commented Jun 15, 2020

Hi @diegojimenes, I am sorry I have been away and just looking at this. I am working on releasing a v4, a week from now, at the latest. However, if you used early versions of the library, you would recall the keys have always been in the manifest files - I am not sure they were safer there and some users wanted to be able to do different things for different environments and didn't have any easy way to do so at the time. Chime in with your thoughts in the replies if you can. Thank you for your contributions.

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

Successfully merging this pull request may close these issues.

2 participants