Just got this from google support regarding the logfile I sent them:
The “RetiredVersion” means that the application is making a request to a version of Google Maps JavaScript API that is already retired. A way to fix this is to replace the version in the request URL. The request URL can also be found in the logs that you have sent:
The v=3.9 is not an updated version. But, this has to be fixed by the Corona team, since they are the ones who set that up.
Another error says “SensorNotRequired”. This means that the request URL is also using a deprecated parameter which is “sensor”. This parameter is no longer working and should no longer be used. This can also be fixed only by the the Corona Team.
In other words: the request that Corona is making to Google Maps uses partly deprecated or non-supported parameters. This has got nothing to do with my error, this is the same for everyone using Corona.
Could you please forward this to your engineers?
UPDATE:
In case anyone wonders, this is the url that should be filled out with the “HTTP referrers (web sites)” choice:
This could be a bit tricky if Corona ever decides to change the name of the html file. In that case, the request will not be valid and no map will be displayed…
@Divergent Monkey, I don’t believe either of those URL parameters are causing an error. I agree that they are old and not doing anything, but they shouldn’t be causing any harm either.
I’ve raised it with engineering, but I’m not sure what the priority will be on fixing it. Since we’ve gone to an open source model, we also are now using GitHub issues to track these types of bugs. Can I get you to visit: https://github.com/coronalabs/corona/issues
And file an issue for this. Perhaps if we can’t get to it in a timely fashion, a community developer who wants to contribute to Corona can look into it.
True, they don’t cause any problems (confirmed by Google support) but if possible, they should be fixed just for the sake of keeping Corona up-to-date. I have creted an issue at the GitHub page. Thanks!
I looked at the source and we are certainly using “mapsKey” in config.lua in the application.license.google table.
If you’re uncomfortable sharing your api key here, you can put together a simple sample project that adds a native.newMapView() to a simple app with your build.settings and config.lua and package that up and a zip file and email it to support@coronalabs.com and we can take a look at it.
@divergent I have never used the maps API until last night. All I did was create an account, add my credit card and added the maps key to the NativeDisplayObjects sample. Clicking on the maps button in that app brings up the map. As you can see in the graph I then tested it at 7, 8 and 9pm EST. I wanted to see if I can fix the other problem I found (but I couldn’t).
@agramonte: what Android version did you test this on? Any issues regarding credit card, billing etc would come after making a valid request but I am not even there yet…
An Android 9 phone. On this one, it throws an error after the map loads with my manual lat long. I think the map is trying to get the current location but doesn’t have permission and the app doesn’t prompt.
An Android 7.1.1 tablet. On this one, it throws a different error, but again it is after the map loads.
What version are you using? I can dig up some of my older phones. I don’t have a 8.x device.
Edit: I think this is a rabbit hole you are going into with no end in sight. Even after you get past your current problem, I notice other problems that I am fairly sure are code related.
@agramonte: I was using version 8.0 when testing. If you want, I could send you the sample app that I sent to Corona support. You could then insert your google maps key instead of mine and see if that works or at least if you get the same error as I do. Let me know, and I can then send it as a private message to you here in your Corona account.
I couldn’t get your code to work but I don’t really understand it. I think you didn’t send me all of it and if this is the same thing you sent to Corona they won’t be able to help you.
local maptest = require("sampleUI.maptest") -- I am missing this file. Maptest is null.
then further down you call this:
maptest.create() -- this is null and you are calling this function from that file I don't have.
I erased everything you had except the first line and put my key in the config:
The zip file submitted to support was complete. Once I added my license key, I was able to build with your mapsKey and the native.newMapView() came up and complained about an issue. I replaced the key with a key I use in a maps based app (I’m doing a Google JavaScript map in a webView because I’m overlaying weather radar on top), rebuilt and re-run your app and I got a map centered on where I live with no error.
So based on my results and Agramonte’s results, this seems to be related to your key and not native.newMapView()
@agramonte: there must be some kind of misunderstanding. The zip file I sent to Corona was exactly the same I sent to you but with my mapsKey removed. The file maptest.lue is in the folder SampleUI.
@Rob: what was the issue that the Map view complained about? When I run it, I get no map at all. What Android version were you using? I don’t get this…