Subscribe to these release notes.
The Google Maps Android API for the Google Maps API 프리미엄 플랜 was first released in August 2013. This page is updated with each release. The changelog below lists the releases by date and includes any new features, bug fixes, and significant performance improvements.
Consult the getting-started guide for information on how to download the most recent version of the API.
October 24, 2016
- Circle filling flickers on fast update of circle radius and center. (Issue 5707)
- Crash if Google Play app is not available. (Issue 4862)
onMarkerClick(Marker)and returning true causes
Marker.isInfoWindowShownto still return false on subsequent marker clicks. (Issue 5408)
- Poor performance when app memory footprint is large. (Issue 5445)
- StrictMode violations shown in log. (Issue 10170)
- Warning when building and installing m4b build:
Ignoring InnerClasses attribute for an anonymous inner class. (Issue 10050)
- The previously-deprecated
getStreetViewPanorama()function is no longer available in the Google Play services SDK. (It is still available in the Google Play services APK that is delivered to Android devices. Existing apps therefore continue running normally until you recompile them.) The
getStreetViewPanorama()function has been deprecated since December 2014. Instead, you should use
StreetViewPanoramaFragment.getStreetViewPanoramaAsync()to get a ready-to-use Street View panorama. See the developer's guide.
September 21, 2016
This release introduces custom styling of the base map. (Issue 5463.) You can pass a JSON style declaration to your
MapStyleOptions, changing the visual display of features like roads, parks, businesses, and other points of interest. This means that you can emphasize particular components of the map or make the map complement the style of your app. Custom styling is available for maps with a map type of
- See the quick guide to styling your map, using night mode as an example style.
- Use styling to prevent certain features from appearing on the map. (Issue 4841)
- Learn the full power of custom styling in the style reference.
Business points of interest (POIs) now appear by default on the map, provided the map type is
normal. (Prior to this release, local POIs appeared on the map, but not business POIs.) Business POIs represent businesses such as shops, restaurants, hotels, and more. See the guide to points of interest.
- You can respond to click events on a POI.
- Getting warning Google Maps Android API:
GLHudOverlay deprecated; draw(): no-op. (Issue 10201)
- Client must have ACCESS_FINE_LOCATION permission to request PRIORITY_HIGH_ACCURACY locations. (Issue 10166)
- Android Nougat developer preview: MapView blank when resized in Multi Window mode and not focused. (Issue 213354)
- Warnings when building and installing the Premium Plan (
m4b) build. (Issue 10050)
Forwarding of lifecycle methods: If you're using the
MapViewclass, and the API is in fully interactive mode rather than lite mode, your app must forward the following activity lifecycle methods to the corresponding methods in the
onLowMemory(). Prior to this release, there was no need to forward
onStop(), but when you recompile your app with the new release, it's essential to forward them too. See the documentation for details.
Improvements to the 프리미엄 플랜 SDK package:
- A top-level README file describing the package contents.
- The top-level directory renamed to
maps_for_business_sdk, making it easier to update existing libraries manually.
- Various improvements to the documentation and file comments, including
clarified comments about permissions in
- Corrected name
- Removed reference to a non-existent source jar in
August 1, 2016
This release introduces a set of new camera change listeners for camera motion start, ongoing, and end events. You can also see why the camera is moving, whether it's caused by user gestures, built-in API animations or developer-controlled movements. Below is a summary of the new listeners. For details, see the guide to camera change events. (Issue 4636)
onCameraMoveStarted()callback of the
OnCameraMoveStartedListeneris invoked when the camera starts moving. The callback method receives a
reasonfor the camera motion.
onCameraMove()callback of the
OnCameraMoveListeneris invoked multiple times while the camera is moving or the user is interacting with the touch screen.
OnCameraIdle()callback of the
OnCameraIdleListeneris invoked when the camera stops moving and the user has stopped interacting with the map.
OnCameraMoveCanceled()callback of the
OnCameraMoveCanceledListeneris invoked when the current camera movement has been interrupted.
You can store an arbitrary data object with a marker using
Marker.setTag(), and retrieve the data object using
Marker.getTag(). For details, see the guide to associating data with a marker. (Issue 4650)
GoogleMap.setMaxZoomPreference()you can set a prefered minimum and/or maximum zoom level. This is useful, for example, if your app shows a defined area around a point of interest, or if you're using a custom tile overlay with a limited set of zoom levels. For details, see the guide to setting minimum/maximum zoom preferences. (Issue 4663)
GoogleMap.setLatLngBoundsForCameraTarget(), you can constrain the lat/lng centre bounds of the focal point of the map (the camera target) so that users can only scroll and pan within these bounds. For example, a retail app for a shopping centre or airport may want to constrain the map to a particular bounds, allowing users to scroll and pan within those bounds. For details, see the guide to restricting the user's panning to a given area.
Improvements and Resolved Issues
- Marker icon anchor breaks with Google Play services 9.0.83. (Issue 9768)
ActivityNotFoundExceptionwhen Google Map is uninstalled/deactivated. (Issue 9483)
OnCameraChangeListeneris deprecated in favour of the new listeners described above - that is,
July 14, 2016
- There are no functional changes in this release. The new library download fixes a packaging bug that caused duplicate file exceptions when depending on recent releases of the Google Play services SDK.
June 29, 2016
- The new
MarkerOptions.zIndex()sets the stack order of a marker in relation to other markers on the map. Read more about marker z-indexes and the effect of z-index on click events. (Issue 4688)
- You can set a transparency factor on tile overlays, so users can see the base map below the overlaid tiles. Read more about tile overlay transparency and the way it works with fade-in animation. (Issue 4765)
- It's now easier to make circles clickable. You can enable and disable
clickability by providing a
CircleOptionsobject with a
clickableoption, or by calling
Circle.setClickable(boolean). Use an
OnCircleClickListenerto listen to click events on a clickable circle. See a code sample.
- NullPointerException: Attempt to invoke virtual method
boolean java.io.File.mkdir()on a null object reference. (Issue 9021)
- NullPointerException: Attempt to invoke interface method
java.util.Iterator java.util.List.iterator()on a null object reference at
com.google.maps.api.android.lib6.d.ei.a(). (Issue 9008)
Marker.setIcon()with resource id on marker outside view makes the marker white. (Issue 9765)
- Setting icon for google map markers will sometimes cause a flicker. (Issue 8531)
Marker.setIcon()causes info window to disappear. (Issue 5419)
- Marker stops dragging if icon is changed in
onMarkerDragStartevent. (Issue 5932)
- Info window no longer highlights on touch when implementing custom
InfoWindowAdapter. (Issue 7809)
- Polylines drawn incorrectly in certain cases. (Issue 5313)
- Strange behaviour drawing polyline. (Issue 5123)
- Polylines which venture near the poles are drawn incorrectly. (Issue 9176)
- NullPointerException when clicking directions toolbar button. (Issue 8817)
- Possible explicit call to the
GoogleMap.getProjection().toScreenLocation(). (Issue 6483)
- When using
SupportMapFragment, the API leaks memory on screen rotation until the map is loaded for the current zoom level. (Issue 5905)
GoogleMap.animateCamera(CameraUpdateFactory.newLatLngZoom(LatLng,zoom))messes up the zoom if cancelled. (Issue 6947)
- The previously-deprecated
getMap()function is no longer available in the SDK. (It is still available in the Google Play services APK that is delivered to Android devices.) The
getMap()function has been deprecated since December 2014. See the release blog post for help with converting from
- Deprecation notice: In a future release, indoor
maps will only be available on
normaltype maps. From that future release, indoor maps will not be supported on
hybridmaps. Even where indoor is not supported,
isIndoorEnabled()will continue to return the value that has been set via
setIndoorEnabled(), as it does now. By default,
true. Subscribe to these release notes for a notification of each release.
February 11, 2016
This release introduces a number of new event listeners:
OnInfoWindowLongClickListenertriggers a callback to
onInfoWindowLongClick(Marker)when the user long clicks on an info window. This listener behaves similarly to the existing click listener.
OnInfoWindowCloseListenertriggers a callback to
onInfoWindowClose(Marker)when an info window closes. For details, see the guide to info window events. (Issue 5469)
OnPolylineClickListenertriggers a callback to
onPolylineClick(Polyline)when the user clicks on a polyline. See the guide to polyline events.
OnPolygonClickListenertriggers a callback to
onPolygonClick(Polygon)when the user clicks on a polygon. See the guide to polygon events. (Issue 4683)
OnGroundOverlayClickListenertriggers a callback to
onGroundOverlayClick(GroundOverlay)when the user clicks on a ground overlay. See the guide to ground overlay events.
- You can enable or disable the clickability of polylines, polygons and ground
overlays by calling
setClickable(boolean)on the relevant object.
- Zoom into maximum level when info window is double tapped. (Issue 4640)
- Android maps v2 marker infowindow RTL text problem. (Issue 5608)
- Correct tiles generated by TileProvider but rendered solid white on the map. (Issue 8084)
- Memory leak. (Issue 8696)
- Turning on the my location layer leaks the Activity. (Issue 8111)
- Google Maps Engine was discontinued at the end of January 2016. For that
MapsEngineLayerclass has been removed from the Google Maps Android API. For more details, see the Google Maps Engine information page.
November 12, 2015
- If you're targeting version 8.3 or later of the Google Play services SDK, you
no longer need the
WRITE_EXTERNAL_STORAGEpermission to use the Google Maps Android API. For details, see the configuration guide.
- All the code samples for the Google Maps Android API are now available
Note that the samples use the
com.google.android.gms.mapspackage, not the
com.google.android.m4b.mapsused with the Google Maps API 프리미엄 플랜. The samples also require the Google Play services SDK, as they use the Location APIs for parts of the demo.
October 1, 2015
- The Google Maps Android API now supports ambient mode for wearable apps. Ambient mode is for always on apps, and is activated when the user is no longer actively using the app, allowing the app to remain visible on the wearable device. The Google Maps Android API provides a simplified, low-color rendering of the map. This mode reduces the power consumption of your app and ensures a consistent look and feel with other ambient apps, such as watch faces.
- Android 6.0 (Marshmallow) introduces a new model for handling permissions, which streamlines the process for users when they install and upgrade apps. If your app targets API level 23 or later, you can use the new permissions model. This is particularly important if you're using the My Location layer in the Google Maps Android API. To learn more, see the documentation for the My Location layer.
June 23, 2015
- Problems when running on devices that have a version of Google Play services older than 7.3.
June 2, 2015
- The Google Maps Android API is now available on Android Wear. Create map-based apps that run directly on wearable devices.
- Problems rendering a map in a
MapViewwhen setting the
zOrderOnTopproperty to true or when embedding a
MapViewin a scrollable container. (Issue 7936)
- Map toolbar always visible in lite mode, even if disabled. (Issue 7947)
May 5, 2015
- A new interface, StreetViewPanorama.OnStreetViewPanoramaLongClickListener, supports long-clicking (tapping and holding down the finger) on a Street View panorama.
- When using the
MapViewclass in lite mode, forwarding lifecycle events is now optional, with some exceptions as noted in the documentation.
- To disable click events on a map in lite mode, you can call
setClickable()on the view that contains the
MapFragment. This is useful, for example, when displaying a map or maps in a list view, where you want the click event to invoke an action unrelated to the map. For details, see the documentation.
showInfoWindow()now works in lite mode as well as full mode.
TileOverlay.clearTileCache()works as expected after returning
NO_TILE. (Issue 4755)
- The API is more selective in its logging behavior in lite mode, when reporting the functions that are not supported in lite mode. It no longer logs the default calls that are made at app startup.
- CameraUpdateFactory is now properly initialized, so you should no longer see
a NullPointerException 'CameraUpdateFactory is not initialized' after
MapView.getMap()returns a valid GoogleMap. (Issue 6499)
- App launch performance is improved, and the main thread is no longer blocked on app launch. (Issue 7532)
- StreetViewPanoramaView no longer requests focus in
onCreate(), thus no longer causing the view to scroll to make Street View visible. (Issue 7566)
- Fixed a resource leak that showed itself in strict mode. (Issue 5992)
- Fixed a NullPointerException that occurred with
setPadding()in accessibility mode. (Issue 7619)
- Fixed a bug crashing apps when loading an icon from an asset. (Issue 7696)
December 8, 2014
- The API offers a new lite mode. When lite mode is enabled, the API serves a bitmap image instead of a fully-interactive map. Lite mode supports all of the map types and a subset of the functionality supplied by the full API. Markers and shapes are drawn on top of the static image client-side, so you still have full control over them. A lite-mode map is useful when you want to display a number of small maps, or a map that is too small to offer meaningful interactivity.
- A new map toolbar is
available in both lite mode and full mode, and is enabled by default in both
modes for apps that are recompiled against the new client library. Tapping on
the toolbar opens the Google Maps mobile app, giving users quick access to
directions and turn-by-turn navigation to the selected marker. In lite mode
the toolbar is static, whereas in full mode it slides in when the user taps a
marker. You can disable the toolbar in both modes, by calling
- The API supports a new
onMapReady()callback which you can set by calling
onMapReady()method is called when the map is ready to be used, and provides a non-null instance of
GoogleMap. This means that you no longer need to check for a non-null map before using the map. See the guide to adding a map.
- Similarly, you can now use
StreetViewPanoramaFragment.getStreetViewPanoramaAsync()to get a ready-to-use Street View panorama. See the documentation.
GoogleMap.CancelableCallback()now behaves correctly when animating/moving the camera. (Issue 5208)
- The visible region's
LatLngBoundsare now calculated correctly in landscape mode. (Issue 5285)
- A marker performance regression is fixed. (Issue 7174)
- The problem with arrowhead shapes in triangulating convex quadrilaterals is fixed. (Issue 6197 - the initial problem reported is now fixed)
getMap()is deprecated in favour of the new
getMapAsync(), described above. Similarly,
getStreetViewPanorama()is deprecated in favor of the new
- For apps that are recompiled against the new client library, the map's
are disabled by default. Up to this release, they have been enabled by
default. You can still enable and disable them by calling
October 16, 2014
- Updated some assets to use material design.
May 13, 2014
- Added Street View for embedding and controlling panoramic 360-degree views.
- Added functionality to indoor maps so that you can respond to indoor and level change events, and replace the level picker with your own. (Issue 5939)
- Improved accessibility features across various embedded controls.
- Enabled the rendering of Chinese characters on Maps Engine Layer infocards.
May 6, 2014
- Support for Google Maps Engine Layers.
Add Google Maps Engine layers as interactive Tile Overlays with the new
- Added a
TileOverlayOptionsto toggle the fade-in of tiles.
- Failed API key authentication attempts are no longer cached. (Issue 6099)
- Added a
setImagemethod to the
GroundOverlayclass that allows you to change the image of a ground overlay. (Issue 4847)
- Added an
setAlphamethod to markers. (Issue 4768)
- Added a
setOnMapLoadedCallbackmethod to the
onMapLoadedis called when the map has completely finished rendering. (Issue 5779)
- Added a
setBuildingsEnabledmethod to the
GoogleMapclass. Buildings are still enabled by default. (Issue 5550)
- The Google logo has been updated.
CameraPositionreturned in a
OnCameraChangeListenernow respects map padding. (Issue 5844)
GroundOverlay.setPositionFromBoundsnow redraws the ground overlay.
- Added a
setPaddingmethod to the
GoogleMapclass 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.getCentermethod. (Issue 4664)
- Added methods to
GooglePlayServicesUtil.getErrorDialogalways returns a dialog, except when Google Play services is available. (Issue 4720)
- Initial release.