Hi
From today i started getting the attached message while trying to open maps in my app on Android.
I thought it was my app so i built an apk from the map code sample and ran it on Android and also got the same message.
I have also tried other devices with the same result.
Does anybody know what is causing this?
I’m not sure what’s going on. Let me get the engineers to look at this…
Same problem here
It’s happening to me too. Looks like Google has changed something. We just did a battery of tests on this app over the past few days and it passed with flying colors. I’ve send this to engineering to look at. It could be a little while before we have an answer.
Rob
It’s only Google has changed his policy about use of Map API’s request and quotas, from June, 22th. You can find information in Google Dev zone. Surely, if you are using geolocation each few seconds with Google API requests, by example, you can imagine that you are wasting a lot of requests, multiplied by users that use your app, etc.
Google changed the rules today. You now have to pass an AppID Key to your mapView where previously you didn’t. They also made some policy changes around API usage.
See: http://googlegeodevelopers.blogspot.com.au/2016/06/building-for-scale-updates-to-google.html
We are looking into how to solve this.
Rob
I’m not sure what’s going on. Let me get the engineers to look at this…
Same problem here
It’s happening to me too. Looks like Google has changed something. We just did a battery of tests on this app over the past few days and it passed with flying colors. I’ve send this to engineering to look at. It could be a little while before we have an answer.
Rob
It’s only Google has changed his policy about use of Map API’s request and quotas, from June, 22th. You can find information in Google Dev zone. Surely, if you are using geolocation each few seconds with Google API requests, by example, you can imagine that you are wasting a lot of requests, multiplied by users that use your app, etc.
Google changed the rules today. You now have to pass an AppID Key to your mapView where previously you didn’t. They also made some policy changes around API usage.
See: http://googlegeodevelopers.blogspot.com.au/2016/06/building-for-scale-updates-to-google.html
We are looking into how to solve this.
Rob