Why Did Google Screw With Maps Again Dec 2017

Subscribe to these release notes. Subscribe

The Google Maps API squad updates this changelog with each new release of the Maps SDK for iOS. The changelog lists the releases past appointment and includes any new features, problems fixes or significant performance improvements.

Consult the getting started guide for information on how to download the most recent version of the Maps SDK for iOS.

Release notes for the Places SDK for iOS are at present no longer included on this folio. Visit Google Places API for iOS Release Notes to encounter what'southward new with the Places SDK for iOS.

Version half dozen.1.1 - March 22, 2022

Bug fixes

  • Fixed an issue where labels disappeared at certain zoom levels when using a custom style.

  • Stock-still an issue where a deadlock could occur when using the Metal renderer.

Version 6.one.0 - March 9, 2022

Features

  • Version bump with no characteristic changes. Added stability improvements and issues fixes to the release.

Versions two.5 and lower deprecation - January 26, 2022

Maps SDK for iOS v2.v and lower are now deprecated and will exist fully decommissioned in January 2023.

Application versions congenital with Maps SDK for iOS v2.v and lower will no longer work after those versions are decommissioned. To avoid disruption for your users, build new versions of your application with Maps SDK for iOS v2.6 or higher and encourage users to upgrade to the newer versions of your app earlier January 2023.

Note that v2.6 supports a minimum of iOS eight, which will exist the new minimum OS supported by Maps SDK for iOS, so users may need to upgrade their version of iOS as well.

Version 2.vi besides supports a minimum of Xcode viii.0, so this deprecation also raises the minimum IDE supported by Maps SDK for iOS.

Exist sure to specify a version in your application'due south build dependencies in order to control which version of the SDK yous build with, which has implications on minimum Os supported for your users. See the guidance on app maintenance best practices which encourages specifying the newest version available in order to access the latest features and bugfixes.

Version 6.0.1 - December 9, 2021

Features

  • Added stability improvements to the release.

Version 6.0.0 - Nov 29, 2021

Features

  • The appearAnimation field on GMSMarker can now be set to kGMSMarkerAnimationFadeIn to cause the marker to fade in when added.

  • (Beta) This release contains a preview of back up for the XCFramework format. You can now install the Maps SDK for iOS as an XCFramework, a binary packet that you can apply on multiple platforms including machines using the M1 chipset.

    Google recommends that you only use this Beta release for development and testing, and rely on the .framework version of the SDK for your production apps.

Bug fixes

  • Fixed an issue where custom tile images with alpha transparency were non existence rendered properly by GMSTileLayer.

Support freezes

  • Support for iOS 11 is at present frozen. The minimum iOS version is now 12.0.

  • The new minimum version of Xcode is 12.0.

Support for Cloud-based maps styling (paid feature) - October 27, 2021

Support for Cloud-based maps styling is mostly available as of Oct 27, 2021 in SDK versions 5.0 and newer. These features, tied to a map ID, volition incur charges against the Dynamic Maps SKU.

Version five.2.0 - October 19, 2021

Features

  • Opt-in support added for using the Metal rendering framework from Apple tree. To try the Metal renderer in your app, phone call [GMSServices setMetalRendererEnabled:Yep] in Objective-C, or GMSServices.setMetalRendererEnabled(true) in Swift before creating any map views.

    If you are Installing the SDK manually, you must also ensure to add the Metal.framework in XCode.

  • Polylines can now have a repeated image, or stamp, over the line. Come across the GMSPolyline Class reference for more information.

Bug fixes

  • Fixed an issue in the OpenGL renderer where marker images were drawn slightly smaller than intended.

Known issues

  • Texture stamp images can appear distorted on polylines when using the OpenGL renderer (Issue 200024432).

  • Polylines with segments that meet at an acute angle may appear differently on the OpenGL or Metal renderers (Issue 200025456).

Freezing support for iOS 12 - October xviii, 2021

In response to changes in our internal dependencies, we are freezing support for iOS 12 in an upcoming major version of Maps SDK for iOS.

Versions of Maps SDK for iOS released beginning the 2d quarter of 2022 will support a minimum of iOS thirteen. Earlier SDK versions volition go along supporting iOS 12.

If your dependencies in CocoaPods or Carthage do not specify a version number, Xcode volition load the newest version and new builds of your app volition not support iOS 12.

Be sure to specify a version in your application's build dependencies in club to command when you raise the minimum supported OS for new versions of your app. See the guidance on app maintenance best practices.

Beta SDK deprecation - August eighteen, 2021

Deprecation

The Beta versions of Maps SDK for Android and iOS are now deprecated and will be fully decommissioned in tardily 2022. A supported version of the Maps SDK for Android and iOS will be made available at least i year prior to the beta SDK being fully decommissioned, which is estimated to occur in late 2022.

The use of the mobile Maps SDKs (Android & iOS) Beta will be degraded per the following schedule:

For Android:

  • As of the engagement of this release annotation, the Maps SDK for Android Beta (versions three.0.0 and 3.one.0) customer library is deprecated.
  • All features of the Beta SDK volition be supported in upcoming releases of the Maps SDK for Android distributed as part of the Google Play services SDK.
  • Back up for the Maps SDK for Android Beta (versions three.0.0 to and 3.i.0) will cease no earlier than Nov 2022.

For iOS:

  • As the appointment of this release note, the Maps SDK for iOS Beta (versions v3.0.0 and v3.10.0) is deprecated.
  • All features of the Beta SDK volition be supported in upcoming releases of the Maps SDK for iOS distributed via CocoaPods and Carthage.
  • Support for the Maps SDK for iOS Beta (versions v3.0.0 and v3.10.0) will stop no earlier than November 2022.

On all platforms, the Beta SDKs will be fully decommissioned, at least one year later on a supported (non-Beta) version is released. We will communicate with you again once the new version is released, so that you can start your migration efforts.

What practise you need to do?

If you are non currently using features in Beta (maps customization, marker collision handling, or polyline customization—Android, iOS), please update your apps to use a supported version as soon as possible before the decommission in late 2022. See the Android and iOS documentation for instructions.

If you are currently using features in Beta, you should await for upcoming releases of the SDKs to migrate to a supported SDK version.

Contact Google Maps Platform Back up with any questions.

Freezing support for iOS 11 - July 20, 2021

In response to changes in our internal dependencies, we are freezing support of iOS 11 in an upcoming major version of Google Maps Platform SDKs for iOS.

Versions of Maps SDK for iOS released beginning the fourth quarter of 2021 will back up a minimum of iOS 12. Earlier SDK versions will continue supporting iOS 11.

If your dependencies in CocoaPods or Carthage do not specify a version number, Xcode will load the newest version and new builds of your app will not support iOS 11.

Exist certain to specify a version in your awarding's build dependencies in order to control when yous enhance the minimum supported Bone for new versions of your app. See the guidance on app maintenance all-time practices.

Version 5.1.0 - June 28, 2021

Issues fixes

  • Stock-still an issue with the generated module map for frameworks without headers.
  • The groundwork color of the map view has been slightly changed.

Support freezes

  • Support for iOS 11 will be frozen in an upcoming major version.

Version 5.0.0 - May 13, 2021

Support freezes

  • Support for iOS 10 is now frozen. The minimum Os is now eleven.0.

Deprecations

  • ARMv7 32-bit compages no longer supported.

This release also includes deprecations and updates for the Places SDK for iOS and Navigation SDK for iOS.

Version 4.ii.0 - March 8, 2021

  • Version bump, no changes. This version is functionally identical to v.4.1.0.
  • Changes are coming in version v.0.0:
    • Support for iOS ten.0 will be dropped in version 5.0.0.
    • To avoid unexpected errors, be sure to specify a version number in your Podfile or Cartfile. This will ensure that your builds remain stable confronting a known version, and volition not switch to the side by side major version until you are set up to update your code.

Version 4.1.0 - Dec 8, 2020

Features:

  • Added crash detection during SDK initialization. In cases where two or more consecutive crashes are detected at initialization fourth dimension, the SDK will effort to restore functionality by automatically resetting cached map tile data. A recovery try event will be logged unless the customer has opted out of abnormal termination reporting via the setAbnormalTerminationReportingEnabled: API on GMSServices.

Version 4.0.0 - October thirteen, 2020

Features:

  • Back up for iOS 9.0 has been dropped. The new minimum is iOS 10.0.
  • The new minimum version of Xcode is 11.7.
  • By default, abnormal SDK terminations, such as app crashes while the SDK is withal running, are monitored. This allows Google to improve SDK stability when applicative. There is also an option to opt-out by using the setAbnormalTerminationReportingEnabled: API on GMSServices.

Version three.10.0 - August 10, 2020

  • Version bump, no changes. This version is functionally identical to v.3.9.0.
  • There is a new Maps Swift Demo App in Google Maps cocoapods.

Annotation:

  • To build apps using the Maps SDK for iOS, the electric current minimum IDE version supported is Xcode 11.5.

Version 3.9.0 - May 26, 2020

Improvements

  • The demo app has been improved.

Bug fixes

  • Fixed issue where apps would crash when resizing map view in some circumstances (Issue 152145655).
  • Stock-still issue where apps would crash when particular custom styles were used (Issue 73344082).
  • Some types of camera motion animations were skipped if initiated before the map view had gone through a layout cycle (Issue 80065881).

Version iii.8.2 - May 18, 2020

Bug fixes

  • Fixed an outcome where apps using the Maps SDK for iOS would crash upon startup.

Version 3.viii.0 - February 18, 2020

  • Version crash-land, no changes. This version is functionally identical to 5.iii.vii.0.

Note:

  • To build apps using the Maps SDK for iOS, the current minimum IDE version supported is Xcode xi.0.

Version 3.7.0 - December 2, 2019

  • Version bump, pocket-size bug fixes only. This version is functionally identical to v.3.6.0.

Version 3.half-dozen.0 - October 28, 2019

  • Version bump, no changes. This version is functionally identical to v.3.5.0.

Version 3.5.0 - October 08, 2019

Resolved Issues:

  • Stock-still missing info window championship in dark mode on iOS 13 (Consequence 137173762).

Version 3.four.0 - September 04, 2019

  • Version crash-land, no changes. This version is functionally identical to v.3.three.0.

Version 3.3.0 - July 29, 2019

Features

  • Added the SDKLongVersion method, which returns the long version of the Maps SDK for iOS.

Resolved Issues

  • Fixed a long-standing intermittent crash on startup related to CoreData cache (Issue 111132807).

Version three.ii.0 - July 8, 2019

Resolved Issues:

  • Fixed an effect when rendering polygons that would result in incorrect shapes existence drawn.
  • Fixed a crashing bug that occurred occasionally when removing overlays from a map.

Improvements:

  • Reduced the amount of work washed when the map is subconscious past other views to amend CPU usage.

Version iii.1.0 - April 16, 2019

Resolved Problems:

  • Indoor maps are now styled to match outdoor maps (Issue 35830576).
  • Fixes an issue where a crash could occur if markup entities were added to the map earlier the map was ready to draw.

Version 3.0.0 - January, 2019

  • Support for iOS viii.0 has been dropped. The new minimum is iOS ix.0.

Known Issues:

  • There is an occasional rendering bug when using the polygon overlay feature.

Quondam Style Removed - November 1, 2018

Features:

  • Removed support for the old basemap style. The opt-in and opt-out API options (run across below) are no longer supported. This applies to all versions of the Maps SDK for iOS. Come across the blog postal service for more information virtually the new style.

New Style Default - June 28, 2018

Features:

  • Enabled the new basemap style by default. Yous can withal opt-out temporarily if you lot need fourth dimension to alter your app to accommodate the new style. If you practise, please follow Issue 72853293 which contains the timeline for end of support of the previous basemap fashion. We will be posting updates there as they are bachelor.

    To opt-out, use the lawmaking snippet below. The best place to do this in your app is right subsequently providing your API key, via GMSServices provideAPIKey. You must be using at least Version 2.6.0 in social club to opt-out. If you had previously opted-in to the new basemap manner, this should replace the code you added to opt-in. Run across the blog post for more information about the new way.

                  NSArray *options = @[@"B3H9HE845CFHYG"]; BOOL didSetApiOptions = [GMSServices provideAPIOptions:options]; NSLog(@"Options were fix: %d", didSetApiOptions);                          

Version 2.seven.0 - April 18, 2018

Improvements:

  • Improved documentation on thread safe of GMSServices.

Resolved Issues:

  • Stock-still crash in GMSDASHStreamingBody (Effect 68701108).
  • Fixed Google Logo positioning in GMSPanoramaView (Issue 72581496).

Annotation:

  • Support for Xcode 8.0 has been dropped. The new minimum is Xcode 9.0.

New Style Opt-In - Feb 13, 2018

Features:

  • Enabled opt-in for the new basemap style. To opt-in, utilise the lawmaking snippet beneath. The best place to do this in your app is right subsequently providing your API key, via GMSServices provideAPIKey. You must be using at least Version 2.half dozen.0 in club to opt-in. See the weblog postal service for more than information near the new style.

                  NSArray *options = @[@"B3MWHUG2MR0DQW"]; BOOL didSetApiOptions = [GMSServices provideAPIOptions:options]; NSLog(@"Options were set: %d", didSetApiOptions);                          

Version 2.six.0 - February 6, 2018

Features:

  • Added a mechanism for developers to enable experimental features.
  • Added a click listener to the My Location dot. This allows developers to respond to interactions with the My Location dot.
  • Added a Source attribute to Panorama searches allowing them to be restricted to outdoor-only results. Note that this feature is experimental and some searches may even so include indoor panoramas (Issue 72250080).

Improvements:

  • Updated the default marker to match the new Google Maps marker.
  • iOS 11 OpenGL crash reduction (Outcome 68699629).

Resolved Issues:

  • Stock-still a compile mistake when the -Wobjc-property-no-attribute flag is used (Result 65561405).

Note:

  • CoreImage has been added every bit a dependency.

Version 2.5.0 - Oct 2017

Features:

  • Added the paddingAdjustmentBehavior belongings to GMSMapView. This property controls how condom area insets interact with padding.

Improvements:

  • Improved iOS 11 & iPhone X support. (Issue 64504919, Outcome 63686068.)
  • GMSMapView and GMSPanoramaView managed subviews are now positioned within iPhone X device safe areas by default.

Resolved Problems:

  • Fixed an consequence where Xcode 9'south Main Thread Checker warns that [UIApplication applicationState] is being called on a background thread. (Issue 63322270.)
  • Fixed an outcome where setting either navigationLinksHidden or streetNamesHidden to YES still resulted in the navigation links and street names actualization. (Issue 64210766.)

Version 2.iv - August 2, 2017

Resolved Issues

  • Addressed a crash when using GMSPanoramaView with an awarding moving to the background land. (Issue 63665236.)

Version 2.3.ane - June 19, 2017

Resolved Issues

  • Stock-still an issue where navigating between panoramas did non consistently heighten GMSPanoramaView consul events. (Consequence 62290311.)
  • Fixed an issue resulting in a crash when UIWebView and GMSPanoramaView are both in the view hierarchy at the same time. (Issue 62279895.)
  • Reinstated the tap-drag zoom gesture for GMSPanoramaView. (Event 62218602.)

Version two.three - May 30, 2017

Improvements

  • The internals of the GMSPanoramaView and associated classes have had a significant overhaul. These changes should mostly give improved performance.
  • Dropped support for iOS 7, which enabled the use of modern core data threading models. This means that applications should be able to utilize -com.apple tree.CoreData.ConcurrencyDebug 1 when debugging with iOS 10 devices. (Result 35829579.)

Resolved Issues

  • Fixed example sensitivity issues with imports in GMSTileLayer.h and GMSPolyline.h. (Issue 35831050.)

Version ii.two - February 14, 2017

Features

  • Added the cameraTargetBounds property to GMSMapView. This holding restricts the camera target to the specified bounds expanse. Subsequent gestures are then also restricted to keep the photographic camera target within the specified bounds.
  • The userData holding of GMSMarker was moved to its parent class GMSOverlay. This enables the holding to be used with the GMSPolyline, GMSPolygon, GMSCircle, and GMSGroundOverlay classes.

Improvements

  • Fixes naming of certain enum cases in Swift. The post-obit enums are affected: GMSMapViewType, GMSFrameRate, GMSMarkerAnimation, and GMSLengthKind.

Resolved Bug

  • Fixed an event where the mapViewSnapshotReady delegate method was sometimes raised too early on (Event 10799.)

Version 2.1.ane - Nov 8, 2016

Resolved Issues

  • Stock-still an issue which acquired many Route Shields to not be displayed when custom styling is active even if the custom styling didn't attempt to manner them.
  • Renamed some symbols which could cause duplicate symbols when using all_load and Firebase. (Issue 10631.)
  • Resolved a trouble where changing any property of polygon, polyline or basis overlay in between taps would crusade tap cycling to pause. This could make it seem impossible to tap through to items underneath. (Consequence 10436.)
  • Fixed cameraForBounds:insets: to respect the currently gear up min and max zoom restrictions. (Issue 10817.)

Version 2.1 - September 22, 2016

Features

  • This release introduces custom styling of the base map (Outcome 4968). You tin can use a JSON style declaration to create a GMSMapStyle instance and pass information technology to the mapStyle holding, to change the visual display of features similar roads, parks, businesses, and other points of interest. You can use styling to emphasize particular components of the map, or make the map complement the style of your app. Styling works but on the kGMSTypeNormal map type.

    • Come across the quick guide to styling your map, using nighttime style as an example style.
    • Utilize styling to prevent certain features from appearing on the map.
    • Learn the full power of custom styling in the manner reference.
  • It is at present possible to apply "night style" to maps, past applying custom styles. (Upshot 5661.)

  • Business points of interest (POIs) now announced by default on the map, provided that the map blazon is kGMSTypeNormal. Prior to this release, local POIs appeared on the map, simply not business concern POIs). Business organisation POIs correspond businesses such as shops, restaurants, hotels, and more. Come across the guide to points of interest.

  • With the addition of business organization points of interest, there is a new optional method didTapPOIWithPlaceID on GMSMapViewDelegate which provides notification when a POI has been tapped. (Issue 8174.)

  • You tin hide POIs on a map past using map styling.

Resolved Issues

  • Renamed the canGoOffline selector internally, to avert triggering simulated positives during submission to the Apple app shop. (Result 10393.)
  • The iconView property of GMSMarker is now correctly marked as nullable. (Issue 10391.)
  • Renderer in iOS has been updated to avoid a race condition which would crusade rendering to non stop in time when an app transitions to background. (Upshot 10224.)
  • GMSPath initFromEncodedPath now returns nil for invalid input (previously invalid input could outcome in a crash). (Issue 10162.)
  • An additional method was added to GMSMapView, which compares two photographic camera positions to decide whether they are close enough to render identically. (Consequence 9494.)
  • GMSCircle volition at present always describe at least a dot for pocket-size radius circles, including radius 0. (Effect 9528.)

Version 2.0.1 - July 29, 2016

Resolved Issues

  • Assortment properties are now correctly typed when accessed from Swift. (Issue 10183.)

Version two.0.0 - July 26, 2016

Improvements

  • This release splits the Places API from the Maps SDK. Previously, if you wanted to utilise the Places API you lot had to include all of GoogleMaps. As a event of the dissever, the final size of the Places API binary is 70% smaller than the previous combined binary. If you are using just the Maps SDK you volition not be affected unless you have pinned your dependency on GoogleMaps to a version earlier than 2.0. In this case, you should update this restriction in your Podfile. If you are using the Places API, see Migrating to Places SDK for iOS.
  • Places SDK demos are at present available separately from Maps demo apps.

Resolved Issues

  • The GoogleMaps binary has been reduced to less than 100MB to avoid exceeding GitHub'south file size limit. (Outcome 9030.)
  • The Maps framework is now available every bit a download for manual installation. For details, see Get Started. (Consequence 8856.)
  • GMSGroundOverlays at present correctly respond to affect input when rotated. (Consequence 9544.)
  • Mark info windows now render consistently (Event 9670, Issue 9819.)
  • Info windows created using the return value of mapView:markerInfoContents: will now correctly respect the height of the returned content rather than always existence square based on the width.
  • Fixed an issue where texture cache limit is exceeded on devices supporting @3x sized images. (Outcome 9859.)

Utility library update - July xix, 2016

Features

  • The new marking clustering utility helps y'all manage multiple markers at different zoom levels on the map. Past clustering your markers, you can put a big number of markers on a map without making the map difficult to read. Get the utility library from GitHub, follow the setup guide, and meet how to implement marking clustering in your app. (Issue 5723.)

Version i.13.2 - May 12, 2016

Resolved Issues

  • Added a workaround to avoid the fake positive for the non-public API imageWithName: selector. (Issue 9704.)

Version ane.xiii.ane - May 02, 2016

Resolved Bug

  • Fixed an application hang when using a UIView with autolayout enabled equally an info window or as a marking iconView. (Issue 9525.)
  • Changed lookUpPlaceID to not phone call its callback twice in error scenarios. (Issue 9310.)

Version i.13.0 - March 29, 2016

Features

  • UIView based markers. Marker content tin can now show advanced animations past providing a custom view bureaucracy to be displayed through the iconView property. See the documentation for details. (Consequence 5203.)
  • Info windows can now have their custom views animated. Set up tracksInfoWindowChanges on the associated marker to Aye to enable real-time updates. (Outcome 5559.)
  • Map rendering now defaults to 60fps on mod iOS devices. Gear up the new preferredFrameRate property on GMSMapView to revert to the old beliefs (Conservative) or a new low frame charge per unit option to salve battery (PowerSave). (Result 5066.)
  • Added mapViewSnapshotReady: to GMSMapViewDelegate which fires when map content, including markers and other overlays, has been fully rendered.
  • Autocomplete widgets in the Places API now provide options for custom styling.

Resolved Issues

  • GMSCoordinateBounds initWithVisibleRegion: now chooses correct bounds for large viewports.
  • Added a workaround to avoid a graphical glitch in snapshots taken using pre iOS vii methods when the My Location push is disabled. (Issue 9173.)
  • GMSAutocompleteViewController now works when used in a storyboard.
  • Added missing Identify Type constants. (Result 8121.)

Version 1.12.3 - February 2016

Resolved Bug

  • Fixed corruption in included bitcode that caused Xcode archive action to neglect. (Issue 9368.)
  • Added a workaround for a limitation in Xcode 6.iv which was failing to compile the included headers.

Version 1.12.2 - February 2016

Features

  • Added place photos to the Places API. (Outcome 8202.)
  • Added structured address components to GMSPlace objects. (Issue 8121.)
  • SDK method signatures have been updated with generics and nullability annotations.

Resolved Bug

  • GMSPlace objects now contain rating and toll level where bachelor.
  • Small-scale bugfixes for the autocomplete widget UI.
  • panoramaView:didMoveCamera: is no longer raised during the panoramaView delegate setter. (Outcome 5630.)
  • Old unused logo files have been removed from the SDK. (Issue 9148.)
  • Tap events on polygons virtually the anti-pinnacle are more reliable.
  • Resolved an effect resulting in unrecognized selector crashes when calling class methods on categories. (Issue 9000.)

Version one.12.ane - February 2016

This version is exactly the same every bit ane.eleven.1. It was released to replace the removed ane.12.0 release.

Version 1.12.0 - February 2016

This version was removed because of errors in the framework and should non be used.

Version 1.xi.1 - December 2015

Resolved Issues

  • Modally presented Place Autocomplete widgets now correctly respect UINavigationBar advent proxy settings.
  • Resolved minor UI bug with the Place Autocomplete widgets.
  • Updated GoogleMaps.parcel info.plist to avoid triggering checks in pre-submission verification. (Issue 8488.)

Version ane.11.0 - Dec 2015

Features

  • Bitcode is at present included in the SDK binary for all device architectures. (Result 8219.)
  • Added Place Autocomplete widget classes.
  • New events for long press on an info window, and closing an info window, accept been added to GMSMapViewDelegate.
  • GMSMapViewDelegate has new events to indicate when map tiles and labels are awaiting and finished rendering. (Issue 5430.)
  • GMSPanoramaViewDelegate has new events to indicate when panorama tiles are awaiting and finished rendering. (Issue 5430.)
  • GMSGroundOverlay now supports an alpha multiplier via the opacity property.
  • Added a holes property to GMSPolygon to let for the subtraction away from the filled area in society to create more complex shapes. (Effect 5464.)
  • At zoom levels greater than fourteen, the maximum tilt has been increased. (Issue 5169.)
  • Added an autocomplete screen to the Place Picker.
  • Dissever autocomplete predictions into chief and secondary text fields.
  • Added a country filter option to GMSAutocompleteFilter.
  • Added a viewport field to GMSPlace.

Resolved Issues

  • Correct handling of taps on overlapping markers. (Issue 7587, Upshot 8591.)
  • Address a race condition dependent crash which tin can happen when an application enters and leaves the background while showing a map. (Issue 7011.)
  • Fix blank maps which can happen when launching an app into the background. (Effect 8510.)
  • Workaround issues with core animation that caused markers to jump. (Issue 8451.)
  • Updated to avoid subtle conflicts with applications which utilize google-toolbox-for-mac.
  • Use the iPhone language instead of the region formatting linguistic communication for Places API results (Issue 8536.)

Notes - Setting GMSMapView selectedMarker to a marker not on the map is at present ignored, always ready the marker's map property before attempting to select it.

Version 1.x.five - October 2015

Resolved Issues

  • Worked around an upshot in the Swift compiler's handling of umbrella header module entries. (Issue 8524.)

Version 1.x.4 - October 2015

Resolved Issues

  • Fixed a crash on iOS 9 when dismissing the place picker without a selection. (Event 8672.)
  • Fixed a crash when using both a GMSMapView and a UIWebView or WKWebView in the view hierarchy at the same time. (Issue 8343.)
  • Recompiled with Xcode vii to avoid raising failed to load optimized model log messages on iOS 9 devices. (Consequence 8459.)

Version 1.10.3 - September 2015

Features:

  • Google logos have been updated.

Resolved Issues:

  • Framework at present ships with the device version of bundles to laissez passer Xcode 7 annal checks. (Result 8568.)

Version 1.10.2 - Baronial 2015

Resolved Issues:

  • Fixed a crash releasing a map view while in background. (Issue 8200.)
  • Resolved a conflict with apps using gtm-session-fetcher resumable downloads.
  • Recompiled with Xcode 6.four to avoid some bugs in Xcode 6.3 compiler.
  • Updated GoogleMaps.bundle info.plist to avoid triggering new checks in pre-submission verification. (Event 8488.)

Version one.10.1 - June 2015

Resolved Issues:

  • Fixed an event where instantiating GMSPlacesClient triggered a request to the user to enable Bluetooth on the device.
  • Miscellaneous improvements to the GMSPlacePicker UI.

Version 1.10.0 - May 2015

Features:

  • The Places SDK for iOS is now included in the SDK framework, and then you lot tin can connect people to places in your iOS apps. If you lot want to use the Places SDK for iOS in your project, please refer to the getting started guide.
  • CocoaPods is at present the fully-supported means of installing and upgrading the Maps SDK for iOS. CocoaPods is an open source dependency director for Swift and Objective-C Cocoa projects. Below is a brusque guide to migrating from earlier versions of the Maps SDK for iOS. Run across the getting started guide for total instructions.
  • A new allowScrollGesturesDuringRotateOrZoom property on GMSUISettings allows you to control whether the user tin can ringlet past panning during multi-touch rotate or zoom gestures. (Issue 7737.)
  • GMSPanoramaView now supports beingness used in storyboard.
  • GMSGeocoder now supports being used while the app is in the groundwork.
  • GMSServices sharedServices can now be chosen while the app is in the groundwork. Note that if the first call to sharedServices occurs while the app is in the groundwork, some async initialization piece of work will be deferred until the start time a map is shown where information technology volition exist performed synchronously.
  • GMSMapView and GMSPanoramaView init letters tin now be handled while the app is in the groundwork. This should remove the terminal case where GMSMapView or GMSPanoramaView could not be used in the background. (Problems 7860, 8007, 8037, 7896, 7951.)
  • GMSMapView and GMSPanormaView delegate properties at present support IBOutlet for easier employ in storyboard. (Progress towards a fix for issue 6866.)

Resolved Issues:

  • mapView:didTapMyLocationButtonForMapView: is now correctly chosen even if no location is available. (Issue 7742.)
  • GMSGroundOverlay now shows correctly when rotated if paradigm aspect ratio doesn't match the selected ground region. (Issue 7772.)
  • Fixed an issue resizing the map on iOS 8.
  • Fixed a rare crash under fast camera changes. (Result 7885.)
  • Map no longer hangs when adding a ground overlay with certain invalid premises. (Issue 7701.)
  • Fixed a crash when texture memory is exhausted by markers. (Issue 7638.)
  • Correctly returns the tapped GMSCircle to mapView:didTapOverlay: for tappable circles. (Consequence 6890.)
  • mapView:idleAtCameraPosition: is now chosen fifty-fifty if there is an ongoing update of the My Location dot. (Issue 7889.)

Notes:

  • Due to an ABI change in the Xcode compiler, Xcode 6.3 is now the merely supported version for compiling confronting Maps SDK for iOS. (Issue 7900.)
  • The minimum target iOS version for Maps SDK for iOS is now 7.0. Version vi.0 is no longer supported.

Migration from 1.9.2 or before:

Versions 1.9.ii and earlier of the Maps SDK for iOS were available as a zip file containing a static framework. There was too the option to install contempo versions from a CocoaPods pod. From version 1.ten.0 onwards, the Maps SDK for iOS is available for installation only via CocoaPods.

If you previously installed the Maps SDK for iOS from a zip file containing a static framework:

  1. Remove all references to the previous framework from your Xcode project.
  2. Follow the instructions in the getting started guide to install the Maps SDK for iOS using CocoaPods.

If you previously installed the Maps SDK for iOS from the Google-Maps-iOS-SDK pod:

  1. Change your pod name to GoogleMaps.
  2. Run pod install.

Version 1.nine.2 - February 2015

Download version 1.9.2.

Resolved Bug:

  • Show right characters for Myanmar identify labels. (Issue 7576)
  • Fixed a small retentiveness leak related to font registration. (Issue 7559)
  • Fixed a large memory leak in rare cases where My Location is enabled and the user rotates the screen.
  • Correctly bear witness ground overlays defined by zoom level which extend beyond more than 180 degrees of longitude.
  • Let selected marker to be prepare during mapView:didTapAtCoordinate:. (Issue 7222)
  • Throw exception rather than crash when map services are initialized while the application is in the background.
  • Raise mapView:willMove: and mapView:idleAtCameraPosition: even for swipe motions which terminal less than 30ms. (Issue 7206)
  • Correctly handle animations starting while a gesture is decelerating. (Issue 7348)
  • Always return an error from GMSPanoramaService callbacks if the panorama is aught.
  • Don't attempt to navigate to an empty panorama if moveNearCoordinate: resolves to nil. (Issue 7109)

Version 1.ix.1 - December 2014

Download version 1.9.1.

Resolved Issues:

  • Added workaround for false positive on userEmail private selector. (Issue 7310)
  • Improved treatment of info windows for iPhone 6+ running applications in scaled mode. (Issue 7323)

Version 1.9.0 - October 2014

Download version i.ix.0.

Features:

  • Support for iOS 8.
  • Support for iPhone 6/half dozen+. (Issue 7140)
  • Support for Swift.
  • UI elements have been updated for material design.

Resolved Problems:

  • Stock-still some retentivity reclamation issues.
  • Improved treatment of application background state transition.

Notes:

  • In guild to improve compatibility with Swift, two geometry library functions have been renamed to avert function overloading. The new names are GMSGeometryIsLocationOnPathTolerance and GMSStyleSpansOffset.

Version 1.viii.1 - May 2014

Download version ane.8.1.

Resolved problems:

  • Resolved GMSTileLayer not displaying. (Upshot 6686)
  • Resolved a rare case where an app would crash when displaying polylines while accessibility features are enabled. (Issue 6689)
  • mapView:willMove: is no longer called alongside a tap gesture. (Issue 6702)
  • Resolved symbol collisions with the Protocol Buffer library.

Version ane.8.0 - May 2014

Version 1.8.0 has been replaced by version 1.8.one and is no longer available for download.

Resolved bug:

  • Resolved threading deadlock prominent on iPhone four running iOS 7.1 or subsequently. (Issue 6484, Result 6524)
  • GMSMapView correctly releases some shared GL state previously causing retentivity leak. (Upshot 5941, Consequence 6265, Result 6629)
  • GMSPolyline no longer crashes in some cases where its path contained more than 1024 segments. (Issue 6542)
  • The consul method mapView:idleAtCameraPosition: is at present only called in one case all user gestures are consummate. (Issue 5718)
  • The Maps SDK for iOS now includes fonts for languages currently unsupported by the iOS system, such as Khmer. (Outcome 5228)
    • These fonts may be safely removed from your GoogleMaps.framework if you have no interest in these regions, just some text may return every bit "[?]".

Version i.7.ii - March 2014

Download version i.7.2.

Resolved issues:

  • GMSPolyline's are no longer grayscale on iOS 7.i.

Version one.7.i - March 2014

Version 1.7.1 has been replaced by Version 1.7.2 and is no longer available for download.

Resolved issues:

  • Heading will only announced on My Location dot when available.
  • Better reduction of colors on gradient or colored polylines at low zoom. (Outcome 6386)
  • The search radius is at present respected when retrieving a GMSPanorama object. via GMSPanoramaService and on GMSPanoramaView structure or move.

Version 1.7 - February 2014

Version 1.7 has been replaced by Version 1.vii.2 and is no longer available for download.

Features

  • Styled polylines: boosted color options via GMSPolyline, including gradients and colors for any number of polyline segments. (Issue 4856)
    • Each polyline may be fatigued with many GMSStyleSpan instances, configuring a unique color or slope over an arbitrary number of segments.
    • Gradient or colour may be specified via a GMSStrokeStyle.
    • GMSPath provides a helper category to decide distance forth a path.
    • GMSStyleSpans helper to use repeated styles along a polyline.
  • GMSGeocoder now provides structured addresses via GMSAddress, deprecating GMSReverseGeocodeResult.
  • Added mutable version of GMSCameraPosition, GMSMutableCameraPosition.
  • Delegate method for user tapping the My Location push.
  • Added GMSMapPoint for linear interpolation between points in Mercator infinite on the Earth.
  • My Location dot now shows compass pointer. (Effect 5325)
  • 3D edifice data is newly bachelor for many places on the Earth.

Resolved issues:

  • GMSPolyline width is much closer to screen width. (Effect 5788, Event 5265)
  • GMSPolyline performance and retentiveness improvements. (Issue 4904)
  • Reduced memory use of OpenGL textures.
  • Floor picker is positioned correctly when My Location push is disabled. (Issue 5742)
  • cameraForBounds:insets: on GMSMapView now correctly accounts for padding. (Outcome 6080)

Notes:

  • To align with other Google Maps APIs, GMSMapView no longer provides helper methods to retrieve previously added overlays, such as markers, polylines and groundOverlays.

Version 1.vi.ii - January 2014

Download Version 1.6.2.

Resolved bug:

  • Resolved a gesture problems effecting total-screen maps on iOS 7. (Issue 6216)
  • Resolved an upshot where overlays were sometimes non initially tappable. (Issue 6143)

Version i.6.1 - December 2013

Version 1.6.1 has been replaced by version 1.6.ii and is no longer available for download.

Resolved issues:

  • Resolved a retentivity leak involving vector tiles.
  • Markers non immediately added to a GMSMapView no longer fail to appear when configured at a later on point. (Issue 6092)
  • GMSMapView/GMSPanoramaView volition now continue to return while your application is resigned. (Issue 5546)

Version i.6 - November 2013

Version 1.6 has been replaced by version 1.vi.2 and is no longer available for download.

Features

  • The Maps SDK for iOS at present supports 64-bit architectures. Both 32 and 64 bit binaries are built into the unmarried GoogleMaps framework. The correct binary will be selected by Xcode based on your build settings. For instructions on building 64-bit applications, please refer to Apple's 64-bit transition guide. (Result 5806)
  • Changed some instances of CGFloat to either a bladder or double where it was more appropriate.
  • Added the power to restrict min and max zoom on GMSMapView. (Effect 5882)
  • Added opacity on GMSTileLayer and GMSMarker.
  • Core Animation on GMSMapView now requires model values to exist fix

Resolved issues:

  • Info windows and tappable regions now rotate correctly with markers. (Consequence 5896, Issue 5969)
  • Padding on a GMSMapView is no longer clamped to its bounds (useful if setting padding on an initially zero-sized map). (Issue 5864)
  • Copyright information now animates when changing GMSMapView size or padding.
  • Info windows are removed if their GMSMarker is removed from a GMSMapView. (Outcome 5856)
  • My Location dot uses the last known location data when enabled. (Event 5590)
  • Resolved 2 rare race atmospheric condition that were causing crashes. (Issue 5795)
  • Resolved an outcome where retain cycles were causing memory leaks on GMSMapView and GMSPanoramaView.

Version 1.five - September 2013

Download Version i.5.

Features

  • This release officially supports iOS 7, and requires iOS 6.0 or later (iOS 5.one is no longer supported).
  • The 'animated' field on GMSMarker is now known as appearAnimation, and may be set to kGMSMarkerAnimationNone (default) or kGMSMarkerAnimationPop.
  • The Maps SDK for iOS now ships with an armv7s slice. (Issue 4745)
  • Several new features for GMSMarker instances:
    • Markers can be made draggable using the draggable property, and new elevate delegate methods have been added to GMSMapViewDelegate. (Effect 4975)
    • Added GMSMarkerLayer, a custom CALayer subclass for GMSMarker that supports animation of marker position and rotation. (Result 4951, Issue 5743)
    • Changing a markers position will cause the marking to animate to the new location.
    • Added support for markers that announced flat against the Earth's surface.
    • Added rotation belongings to rotate markers effectually their ground ballast.
    • The UIImage used by GMSMarker now supports the images and duration properties, and will animate images with multiple frames.
    • The UIImage used by GMSMarker now supports alignmentRectInsets, and will adjust groundAnchor, infoWindowAnchor, and the tappable region. (Issue 5729)
  • Added padding on GMSMapView, allowing y'all to bespeak parts of the map that may be obscured past other views; setting padding re-positions the standard map controls, and the photographic camera and camera updates volition use the padded region. (Consequence 5466, Issue 5728)
  • GMSPanoramaView and GMSPanoramaService now support searching for panoramas with custom radius.
  • Added cameraForBounds:insets: to GMSMapView, assuasive construction of a GMSCameraPosition for the map from a specified GMSCoordinateBounds.

Resolved issues:

  • The "My Location" button now clips within GMSMapView. (Issue 5764)
  • Reduced memory usage of GMSMapView through less aggressive tile caching. (Issue 5202)
  • Reduced the time taken to obtain GMSServices by moving some startup tasks to a background thread; obtaining this object early in your application (before creating a GMSMapView or other objects) may improve functioning. (Effect 5640)
  • Polylines may now be drawn twice, as required, if they have very large longitudinal bridge.
  • Resolved a rounding error with very small polygons far from latlng (0,0). (Issue 5413, Outcome 5654)

Migration from 1.4.x:

  1. Version 1.5 requires iOS half-dozen.0 or afterward. Applications that must support iOS v.ane should keep to use the nearly recent 1.iv.x release.
  2. The animated property of GMSMarker has been replaced with the new field: appearAnimation. To maintain previous behavior, supplant all references to the blithe property equally follows:

                  marker.animated = YES;                          

    Should be replaced with:

                  mark.appearAnimation = kGMSMarkerAnimationPop;                          
  3. Changes to the GMSMarker.position property are now animated. You can disable this animation with the following sample code.

                  [CATransaction brainstorm]; [CATransaction setDisableActions:YES]; mark.position = ...; [CATransaction commit];                          

Version i.four.three - August 2013

Resolved issues:

  • Resolved several causes of modifying markers that could cause 'ghost' markers to announced. (Outcome 5751)
  • Resolved excess texture apply when modifying animated markers. (Upshot 5756)

Version 1.4.2 - August 2013

Resolved issues:

  • Fixed a rare case where modifying an blithe marking could cause 'ghost' markers to appear.
  • Prioritized markers over other overlays for tappability.

Version ane.4.i - Baronial 2013

Features

  • Tappable markers inside GMSPanoramaView using the panoramaView:didTapMarker: delegate method on GMSPanoramaViewDelegate. (Issue 5622)
  • Added GMSPanoramaLayer, a custom CALayer subclass for GMSPanoramaView that supports animation of the panorama camera.
  • GMSPanoramaCamera supports custom field of view (FOV).
  • Programmatic access to the floor picker allows y'all to enable or disable the selector, and fix which floor should be displayed. (Issue 5623, Consequence 5666)
  • GMSTileLayer now supports high DPI tiles for apply on a Retina device. (Issue 5402)
  • GMSMapView.photographic camera is now observable via KVO.
  • Added fitBounds:withEdgeInsets: to GMSCameraUpdate. (Event 5475)
  • The default behavior of a GMSMapView to eat all gestures within its bounds may now be disabled via consumesGesturesInView. (Consequence 5552)
  • Expanded GMSGeometryUtils to include additional helper methods.
  • GMSServices may be held past applications to maintain cache and connection to Google; this tin can improve performance when creating and destroying many maps.
  • Improved visuals when resizing a GMSMapView via UIView animation methods.

Resolved bug:

  • Fixed crash issues during retentiveness alarm (related to indoor). (Effect 5637)
  • Fixed crash bug with indoor maps on iOS 5.i. (Issue 5664)
  • Performance improvements when using hundreds of GMSMarkers.
  • Reduced retentiveness footprint of GMSMapView.
  • Touch target for GMSMarkers matches the size and shape of the marker when the GMSMapView is tilted. (Issue 5273)
  • GMSMapView will no longer render a single frame of blackness in some cases (noticeable eastward.g., inside UISplitViewController on iPad).
  • Street View imagery is now adjusted correctly for tilted base data (e.g., information taken past a Street View car on a slope).
  • Geodesic interpolation has been tweaked to be more correct.
  • Fixed incorrect GMSGroundOverlay sizing that prevented some images from displaying. (Issue 5663)
  • fitBounds:withPadding: on GMSCameraUpdate now correctly applies padding to all edges of the premises; previously information technology used 1/ii padding on each border.

Version one.iv.0 - July 2013

Features

  • Support for Google Street View imagery, with coverage in fifty+ countries.
    • Added GMSPanoramaView, a viewer for Street View imagery, that enables both programmatic and user control.
    • GMSMarkers can be shared between GMSMapView and GMSPanoramaView.
    • GMSPanoramaService may be used to load panorama information ahead of display.
  • Indoor floor plans and a floor selector control will now be displayed when bachelor.
  • Updated map pattern inspired past the new Google Maps.
  • Info windows now show at 1:1 resolution on the screen regardless of tilt.
  • Boosted consul methods on GMSMapViewmapView:willMove: and mapView:idleAtCameraPosition: — allow you lot to observe the start and stop of photographic camera move, respectively.
  • An improved await and feel for polylines and polygon stroke.
  • Added a zIndex property on all overlays. Z-Indexes are calculated in two groups: GMSMarkers and all other overlays.
  • Added GMSGeometryUtils methods for heading, distance, offset etc. with respect to points on the Globe.
  • To align with other Google Maps APIs, GMSGroundOverlay no longer supports the zoomLevel property. You lot can use the helper method groundOverlayWithPosition:icon:zoomLevel: to migrate existing code.

Resolved issues:

  • Improved the tappability of GMSPolygon.
  • The compass now disappears when the map returns to zero bearing for any reason, including animation.
  • Resolved crash issue when creating a nada-sized GMSPolygon.
  • Resolved an event where active gestures could cause a GMSMapView to not exist released until deceleration completed.
  • Info windows no longer let taps to pass through them.
  • Accessibility elements on GMSMapView are now hidden by default. Run across the migration steps below if y'all wish to enable these elements.

Migration from 1.three.10:

Version i.4 introduces changes to accessibility and ground overlays. If you make apply of either of these in your application, you will accept to modify whatever existing code as follows:

  1. If your application relies on the accessibility elements of GMSMapView, prepare the accessibilityElementsHidden property to NO.

                  mapView_.accessibilityElementsHidden = NO;                          
  2. Replace direct references to the GMSGroundOverlay zoomLevel property with the new groundOverlayWithPosition:icon:zoomLevel: convenience method. Alternatively, you lot can position the image with a geographic bounds. The beneath code samples are equivalent.

Version 1.3.ten assigned zoomLevel directly.

          GMSGroundOverlay *groundOverlay = [[GMSGroundOverlay alloc] init]; groundOverlay.icon = [UIImage imageNamed:@"newark_nj_1922.jpg"]; groundOverlay.position = CLLocationCoordinate2DMake(twoscore.742, -74.174); groundOverlay.zoomLevel = 13.6;                  

In version 1.iv and afterward, y'all can use the convenience method.

          GMSGroundOverlay *groundOverlay = [GMSGroundOverlay groundOverlayWithPosition:newark                                                                  icon:[UIImage imageNamed:@"newark_nj_1922.jpg"]                                                             zoomLevel:xiii.6];                  

From this release, we recommend that you position your ground overlay past defining its south west and northward due east corners.

          CLLocationCoordinate2D southWest = CLLocationCoordinate2DMake(40.712216,-74.22655); CLLocationCoordinate2D northEast = CLLocationCoordinate2DMake(twoscore.773941,-74.12544); GMSCoordinateBounds *overlayBounds = [[GMSCoordinateBounds alloc] initWithCoordinate:southWest                                                                         coordinate:northEast]; UIImage *icon = [UIImage imageNamed:@"newark_nj_1922.jpg"]; GMSGroundOverlay *overlay =     [GMSGroundOverlay groundOverlayWithBounds:overlayBounds                                          icon:[UIImage imageNamed:@"newark_nj_1922.jpg"]];                  

Version 1.3.i - June 2013

Resolved issues:

  • Shows all tiles when animative across the antimeridian
  • Performance improvements while zooming
  • Touches are consumed more agressively past GMSMapView
  • Stock-still amalgam a GMSMutablePath via pathFromEncodedPath:
  • Restores OpenGL land correctly in GMSMapView in applications that also use GLKView

Version one.3 - May 2013

Features

  • Support for custom tile overlays (image-based) via GMSTileLayer.
  • Anti-aliasing for GMSPolyline and GMSPolygon stroke.
  • Support for 'invisible' base map tiles via kGMSTypeNone.
  • Basic back up for CAAnimationGroup on GMSMapLayer.

Resolved problems:

  • Performance improvements with large numbers of overlays.
  • Resolved excessive retention utilize when device was locked/unlocked while an info window was displayed
  • Animations are stopped when a user performs a gesture
  • Animations stop whatsoever active gesture (eastward.k., a pan)
  • Resolved crash issue with setting/clearing My Location dot
  • GMSPolyline and GMSPolygon now support greater precision at high zoom
  • GMSPolyline and GMSPolygon use the correct blastoff values
  • Touches are consumed by GMSMapView, allowing use within objects such every bit a scroll view

Version one.2.two - April 2013

Resolved issues:

  • Tappable regions for GMSMarker fixed.
  • Overlays are no longer able to render on one-half pixels.
  • Footing overlays appear underneath the My Location dot.
  • GMSPolyline strokeColor is no longer erroneously deallocated.

Version 1.2 - April 2013

Features

  • You can now create overlays directly, without the need for an associated options class. The GMS...Options classes have been removed from this release.
  • Map overlays, such as GMSMarker and GMSPolyline, now inherit from a shared GMSOverlay class.
  • Added support for ii new overlays, GMSPolygon and GMSCircle.
  • The width and stroke properties of GMSPolyline accept been renamed to strokeWidth and strokeColor to parallel GMSPolygon and GMSCircle.
  • Overlay types may now be subclassed.
  • Additional helper methods take been added to GMSCoordinateBounds. The including method has been renamed to includingCoordinate, added includingBounds.
  • A GMSMarker may exist blithe when added to a map.
  • GMSCameraUpdate to create camera update objects, including operations to ready a camera that presents a specified GMSCoordinateBounds
  • GMSUISettings may be used to add a compass or "My Location" push (disabled by default).
  • Non-marking overlay types are tappable (see GMSMapViewDelegate).
  • The default marker image has been changed to the Google Maps for iOS marker.
  • Added markerImageWithColor: to create tinted versions of the default mark.
  • GMSMapLayer, the CALayer subclass for GMSMapView, now supports modification of its camera backdrop, allowing for advanced animation effects.
  • semaphore_wait_trap issue resolved.

Resolved problems:

  • visibleRegion now reports correctly sized region on Retina Devices.
  • Double-tap to zoom now centers around tapped point.
  • Disabling pan via UISettings now prevents movement with zoom gestures.
  • GMSPolyline performance is improved for big polylines.
  • GMSMapView may be subclassed.
  • My Location dot appears underneath markers.
  • Operation improvements when using the My Location dot.
  • Grayscale polylines now render correctly.
  • Calling renderInContext: on the GMSMapView layer now renders correctly; this allows for snapshots and UI effects.
  • The default behavior when a marking is tapped has been updated to also pan the camera to the marker'due south position.

Migration from 1.1.x:

When upgrading to the about recent version, yous volition have to alter any existing code every bit follows:

  1. Supersede references to the width and stroke backdrop of GMSPolyline with strokeWidth and strokeColor. The behavior is otherwise the aforementioned.
  2. Replace calls to the including method of GMSCoordinateBounds with a phone call to includingCoordinate.
  3. Version ane.ii simplifies overlays (items added to the map) past allowing yous to set overlay options directly on the object, instead of first creating an overlay options object. This change impacts existing code as follows:
    • Remove all references to GMSGroundOverlayOptions, GMSMarkerOptions or GMSPolylineOptions.
    • GMSGroundOverlay, GMSMarker and GMSPolyline are at present physical classes, not protocols. Specify them as GMSMarker *, instead of id<GMSMarker>.
    • Add an overlay to the map by setting its map holding instead of calling the add together...Overlay method.
    • Remove an overlay from the map by setting its map holding to cipher (rather than calling remove).
    • Values previously attack properties of an options object should at present be set on the object itself.

Below is an example of how to add together a polyline to the map in version i.1:

          GMSPolylineOptions *lineOptions = [GMSPolylineOptions options];  GMSMutablePath *path = [GMSMutablePath path]; [path addCoordinate:CLLocationCoordinate2DMake(37.35, -122.0)]; [path addCoordinate:CLLocationCoordinate2DMake(37.45, -122.0)]; lineOptions.color = [UIColor blueColor]; lineOptions.path = path;  id<GMSPolyline> line = [mapView_ addPolylineWithOptions:lineOptions];                  

The equivalent code in version i.2.0 and afterward is:

          GMSMutablePath *path = [GMSMutablePath path]; [path addCoordinate:CLLocationCoordinate2DMake(37.35, -122.0)]; [path addCoordinate:CLLocationCoordinate2DMake(37.45, -122.0)];  GMSPolyline *line = [GMSPolyline polylineWithPath:path]; line.strokeColor = [UIColor blueColor]; line.map = mapView_;                  

Version ane.1.2 - March 2013

Resolved problems:

  • Updated the SDK to apply libc++ instead of libstdc++.
  • Improved back up for including a GMSMapView and GLKView in the aforementioned app.

Migrating from v1.ane.1 or earlier:

Version 1.1.2 and later use libc++ instead of libstdc++. To upgrade to the most recent version of the SDK, practice the following:

  1. In the Projection Navigator, replace the previous framework with the most recent framework.
  2. Select your project from the Project Navigator, and choose your application'south target.
  3. Open up the Build Phases tab, and within Link Binary with Libraries:
    • Remove libstdc++.dylib.
    • Add libc++.dylib.
  4. Recompile your project.

Version i.1.1 - March 2013

Features

  • Improved the messages that are logged to the console when a invalid cardinal is used or a connection mistake occurs.
  • Added multi-line snippet support for GMSMarker.

Resolved issues:

  • GMSMapView could return a nil camera.
  • Multiple GMSMapView instances no longer 'camera crosstalk'.
  • The SDK independent unresolved external references.
  • A GMSMarker with an empty title and snippet no longer shows an empty info window.

Version 1.1 - February 2013

Features

  • The points of a GMSPolyline (and GMSPolylineOptions) are now specified as a GMSPath and congenital via a GMSMutablePath, rather than addVertex: etc
  • GMSPolyline may now be specified as geodesic.
  • animateToCameraPosition: method on GMSMapView.
  • GMSProjection provides containsCoordinate: and visibleRegion helpers.

Resolved issues:

  • GMSCameraPosition and animateToLocation: now clench/wrap latitude/longitude respectively; similarly, bearing is clamped to 0 <= begetting < 360
  • GMSGroundOverlay may exist modified afterward creation.
  • GMSPolyline may cross the antimeridian
  • Resolved a marker sorting issue.

Version 1.0.ii - Jan 2013

Features

  • GMSCamera was changed to GMSCameraPosition
  • Removed requirement to call start/stopRendering
  • Improved texture retentivity handling
  • Added UISettings to command gesture availability
  • Added Ground Overlays

Resolved issues:

  • Fixed: GMSMapViewDelegate's mapView:didTapInfoWindowOfMarker: method is unreliable
  • Selected markers are automatically brought to forepart
  • Polylines now render at a constant size regardless of the zoom level

Version 1.0.one - Dec 2012

  • Initial release aslope Google Maps for iOS.
  • Support for 3D maps, rotation, tilt, 3D buildings, markers, polylines.
  • Satellite and terrain tiles, traffic data, and other features.

moorebete1951.blogspot.com

Source: https://developers.google.com/maps/documentation/ios-sdk/releases

0 Response to "Why Did Google Screw With Maps Again Dec 2017"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel