Fixed
Status Update
Comments
an...@google.com <an...@google.com> #2
Can you please put together a simplified, reproducible case (http://sscce.org/ ) and add it to a git hosting provider (e.g. github, bitbucket, etc.) ?
*******************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*******************************************************
*******************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*******************************************************
co...@outlook.com <co...@outlook.com> #3
Honestly, I don't believe you need an example to be able to reproduce and verify this issue. It works properly with version 2.6.0 and previous ones.
an...@google.com <an...@google.com> #4
Thanks for reporting this issue. We have verified and logged it internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.
[Deleted User] <[Deleted User]> #5
The same bug exists when you call mapView.animate(to: camera) or mapView.moveCamera(update). Rolling back to 2.6.0 fixes the problem.
[Deleted User] <[Deleted User]> #6
I can't believe this is still classified as P4-S4 when it has a huge impact on user experience.
[Deleted User] <[Deleted User]> #7
Could you please provide an update? Thank you.
ni...@gmail.com <ni...@gmail.com> #8
Same here, I had to go back to 2.6.0 to make it work. How come such a bug is not taken seriously?
di...@google.com <di...@google.com>
[Deleted User] <[Deleted User]> #9
Could you please provide an update? Thank you.
di...@google.com <di...@google.com>
ra...@google.com <ra...@google.com>
[Deleted User] <[Deleted User]> #10
works on iPhone X, iOS 13.3
does not work on:
iPhone 8, iOS 13.3
iPhone 6S, iOS 13.2.3
does not work on:
iPhone 8, iOS 13.3
iPhone 6S, iOS 13.2.3
Description
Using GMSMapView's animate(with:) method passing a GMSCameraUpdate like GMSCameraUpdate.fit(bounds) shows an incorrect map frame with missplaced center.
What should happen instead?
Passing a bounds argument corresponding to a previously added polyline should end up showing the entire polyline centered on the map.
Steps to reproduce the problem:
1. Use Google Maps SDK for iOS version 2.6.0.
2. Place a GMSMapView instance on any UIViewController instance.
3. Add a GMSPolyline instance with any GMSPath.
4. Animate GMSMapView with GMSCameraUpdate.fit(bounds) where bounds is the path of the previously added GMSPolyline, like GMSCoordinateBounds(path: path).
5. Run your app and you will see your polyline completely centered on the map and perfectly displayed.
6. Update Google Maps SDK for iOS to version 2.7.0 and run the app once again without modifying anything in code. The map view is incorrect and polyline is not centered on the map.
Operating system version: iOS 11.3
Google Maps SDK for iOS version: 2.7.0
Hardware model: any iPhone