search

akvo / akvo-flow-mobile

Akvo Flow app
GNU General Public License v3.0
18 stars 16 forks source link

Issue with Android maps when debugging #496

Closed valllllll2000 closed 7 years ago

valllllll2000 commented 7 years ago

This is not urgent but still would be useful to setup.

When running the app in debug mode using android studio I cannot see the maps correctly and get the following error logs:

11-10 12:14:42.591 7178-7251/org.akvo.flow E/b: Authentication failed on the server.
11-10 12:14:42.591 7178-7251/org.akvo.flow E/Google Maps Android API: Authorization failure.  Please see https://developers.google.com/maps/documentation/android-api/start for how to correctly set up the map.
11-10 12:14:42.592 7178-7251/org.akvo.flow E/Google Maps Android API: In the Google Developer Console (https://console.developers.google.com)
                                                                      Ensure that the "Google Maps Android API v2" is enabled.
                                                                      Ensure that the following Android Key exists:
                                                                        API Key: (.....removed api key ....)
                                                                        Android Application (<cert_fingerprint>;<package_name>): (....removed fingerprint.....);org.akvo.flow

The reason for that is the debug key I am using has not been added to the google maps list of accepted keys. How to fix it? There are 2 options: 1) We could add my debug key to the maps api keys (i would need access to the maps developer console console). Then all the other contributors will also have to add their keys fingerprint. 2) We could have one debug key shared among all contributors and it could be committed even to the repo (the debug key does not allow publishing the app to playstore or in production mode). In that case we only need to add that key once and then all future developers using that debug key will be covered.

valllllll2000 commented 7 years ago

This has been solved by using the same debug keystore in issue 509