1

Google release Google Maps API v.3.27 yesterday and GMLib appears to be broken. When I specify v3 and the current release of the Google API (v3.27) is used, the map does not appear. If I specify v.3.26 in my map.html, the application works correctly.

I am using GMLib 1.5.3 and the problem can be reproduced in the MegaDemo project included in the GMLib files.

Mark
  • 11
  • 2
  • Default. GMLib v1.5.3 uses the Maps API v3.17. Not tested on newer versions of this API and some properties of objects have been deleted – cadetill Feb 16 '17 at 08:14
  • I understand, however according the Google Maps API documentation, they will retire a previous frozen version when a new one is introduced. If you specify 3.17, it now uses 3.26. At the next reelease (3.28), version 3.27 will be the frozen version and you won't have the option to use a version that works with the current version of GMLib. https://developers.google.com/maps/documentation/javascript/versions#version-rollover-and-version-types – Mark Feb 16 '17 at 15:51
  • cadetill - is there a plan to address this issue? Once Google releases 3.28 from experimental next month, the 3.27 version will be frozen and is the version the API will serve even if you specify 3.17 (or any other earlier version). Users of GMLIB probably don't realize their map application will break. – Mark Apr 20 '17 at 21:15
  • I will try to up to date this week. However, you have the source code you can do it yourself ;-) – cadetill Apr 21 '17 at 13:42
  • I started to take a look at this issue. Do you have a recommended way to capture the console log from the twebbrowser? Thanks. – Mark May 01 '17 at 16:05
  • Tested into 3.28 and work fine. I have update GMLib version on GitHub :-) – cadetill May 02 '17 at 16:52

1 Answers1

0

You can download the newest version 1.5.4 from here

Community
  • 1
  • 1
Yon
  • 31
  • 7