Google Maps Android API v2

Google Maps Android API v2 Release Notes

This page will be updated with each new release of the Google Maps Android API v2. The changelog will list releases by date and will include any new features, bug fixes or significant performance improvements.

Consult the Getting Started documentation for information on how to download the most recent version of the Google Maps Android API v2.

January 2014

Features

  • Added a fadeIn flag to TileOverlayOptions to toggle the fade-in of tiles.

Resolved Issues

  • Failed API key authentication attempts are no longer cached. (Issue 6099)

October 2013

Features

  • Added a setImage method to the GroundOverlay class that allows you to change the image of a ground overlay. (Issue 4847)
  • Added an alpha option and setAlpha method to Markers. (Issue 4768)
  • Added a setOnMapLoadedCallback method to the GoogleMap class. onMapLoaded is called when the map has completely finished rendering. (Issue 5779)
  • Added a setBuildingsEnabled method to the GoogleMap class. Buildings are still enabled by default. (Issue 5550)
  • The Google logo has been updated.

Resolved Issues

  • CameraPosition returned in a OnCameraChangeListener now respects map padding. (Issue 5844)
  • GroundOverlay.setPositionFromBounds now redraws the ground overlay.

September 2013

Features

  • Added a setPadding method to the GoogleMap class that allows you to indicate parts of the map that may be obscured by other views. Setting padding re-positions the standard map controls, and camera updates will use the padded region. (Issue 4670, Issue 5321)
  • Added the LatLngBounds.getCenter method. (Issue 4664)
  • Added methods to Marker:

Resolved issues

  • GooglePlayServicesUtil.getErrorDialog always returns a dialog, except when Google Play services is available. (Issue 4720)

August 2013

Resolved issues

August 2013

Features

  • Added a snapshot() method to the GoogleMap class that returns a bitmap of the current map. Snapshots can be used elsewhere on the device, or in your app, to show a map when a MapFragment or MapView would not be feasible; they shouldn't be transmitted off the device. (Issue 4898)
  • Added a click event listener to the My Location button. (Issue 4789)

Resolved issues

  • Fixed info window sprites for xxhdpi devices. (Issue 5439)
  • Clickable regions on custom markers more closely match the size of the custom image. (Issue 5368)
  • Added implementations for canScrollHorizontally and canScrollVertically. This improves behavior for maps appearing inside of scrollable containers, such as ViewPager.

July 2013

Features

  • The MAPS_RECEIVE permission is no longer required. You can remove this permission from your manifest.
  • Updated map design inspired by the new Google Maps.
  • You can now save Maps API Parcelable classes (e.g. LatLng, GoogleMapOptions) in the state Bundle of a MapFragment. (Issue 4713)

Resolved issues

  • Fixed an issue that would cause a NullPointerException. (Issue 5395)

May 2013

Features

  • Added the Marker.setIcon method. (Issue 5075)
  • Added the Marker.setAnchor method.
  • Android emulator support. (Issue 4627)
  • My Location layer is backed by the fused location provider in the Android Location API. Location accuracy should be greatly improved. (Issue 4660, Issue 4682)

Resolved issues

  • A number of memory leaks were fixed. (Issue 4766, Issue 4703)
  • OpenGL ES 2.0 feature requirement is no longer required to be included in AndroidManifest. Note: OpenGL ES 2.0 is still required for Maps to function. (Issue 4699)
  • MapView(Context) constructor no longer throws a NullPointerException. (Issue 4903)
  • LayoutParams no longer need to be set on a RelativeLayout returned by an InfoWindowAdapter. (Issue 4748)
  • OnMapClickListener is now called when a user clicks on a map icon (e.g. transit station). (Issue 5062)
  • The Google Maps application is no longer required to be installed. (Issue 4914)
  • Pre-multiplied alphas in ground overlays are now blended correctly. (Issue 4924)
  • Documentation added for zOrderOnTop. (Issue 4812)

Note: OnMyLocationChangedListener and GoogleMap.getMyLocation() are deprecated in favor of the new Android Location APIs.

March 2013

Resolved Issues

February 2013

Features

  • Added OnMyLocationChangeListener, which is called when a change in location is detected. (Issue 4644)
  • Added the BitmapDescriptor.fromPath method. (Issue 4637)
  • Added support for Circle overlays. (Issue 4819)
  • Added support for the hybrid map type when using XML attributes.

Resolved issues

  • Improvements to memory management, minimizing memory leaks. (Issue 4766)
  • OpenGL ES 2.0 feature requirement is no longer required to be included in AndroidManifest. Note: OpenGL ES 2.0 is still required for Maps to function. (Issue 4699)
  • Fixed blurry markers due to non-rounded pixel alignment. (Issue 4667)
  • Greatly improved performance of adding many markers. (Issue 4669)
  • Fixed an occasional 1px gap in a info windows. (Issue 4666)
  • Calling MarkerOptions.visible(false) will now make the marker invisible. (Issue 4677)
  • Invisible markers are no longer clickable. (Issue 4668)
  • Copyrights are no longer visible when mapType is set to MAP_TYPE_NONE. (Issue 4834)
  • Fixed incorrect sizing of GroundOverlays. (Issue 4723)
  • Improved recovery from gaining network connectivity. This fix requires the ACCESS_NETWORK_STATE permission. (Issue 4817)
  • Fixed disappearing info window while the map is moving. (Issue 4657)
  • Info window is now selectable after being double tapped. (Issue 4641)
  • The double tap and drag gesture is disabled when zoom gestures are disabled. (Issue 4694)
  • Several improvements to product documentation. (Issue 4675, Issue 4676, Issue 4653)
  • Polygon vertices may now be ordered in clockwise or counterclockwise order.
  • CancelableCallback now calls onCancel() instead of onFinish() when interrupted by a user interaction.
  • Text labels are now sized correctly on tablets.
  • TileFetcher no longer continues to fetch after a TileOverlay is removed from the map.

December 2012

  • Initial release. Included as part of Google Play Services SDK.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.