I'm getting a Google Maps error when trying to import a G-Metrix log (gpx file). I see the map for a fraction of a second and then it shows the following message (see attached image). Has this happened to anyone else and have you been able to resolve the issue? ciq.forums.garmin.com/.../1383490.png
I was able to get the "For Development Purposes" overlay everyone seems to be getting. It looks like our server was still sending a lot of people (everyone?) the old version of the maps, so we made some corrections server side, and I no longer see the map overlay. Some of our other testers are still seeing it though, so there is still some additional fix up to do.
The person in our office who had the problem was using a Mac. In Mac VirbEdit you can select "Reload" from the map's context menu and this should clear any locally stored copy of the maps page. We have not seen this issue occur on Windows since our fix. If you are still experiencing any issues with the map, please let me know
Well guess what...After having no success whatsoever with the verbedit maps I decided to uninstall verbedit using the Microsoft programme uninstall tool and download the software again. On starting the install it still found something and asked if I wanted to uninstall, so I said yes. When I installed then it went in OK without referring to net framework versions or java scripts which would now have already been there. On opening up verbedit now and loading a video and fit file it all works perfectly including the maps and synchronising functions. I am a happy bunny finally. What is still disappointing though is no response from Garmin at all. Ah well....
What is still disappointing though is no response from Garmin at all. Ah well....
There are two discussions about this same issue; one is in the Mac forum and the other here in the Windows forum. Garmin has been responsive and provided updates as they became available, probably more so in the Mac forums. Rather than bash on the developers, give them a bit of credit for recognizing there was an issue and addressed the problem that didn't require any new updates to the software.
