Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I would like to go OpenSource with my native Android App VolcanoReport. There is a Google Maps API key used for the MapView. I would like to know if there are security or license issues when I publish the source code containing the API key.
As far as I can see this is not in conflict with the Google license and the key cannot be misused as long as I keep my certificate used to build the app private.
Am I right or are there reasons why the code with the API key should not be published?
AFAIK, your analysis is correct. Anyone reusing your source code would need their own signing key and, hence, their own Google Maps API key. I have Maps API keys embedded in many of my book samples, and I am unaware of any impacts that has had.
OTOH, volcanoes might take this opportunity to accuse you of invading their privacy… 🙂