Fixed
Status Update
No update yet.
Comments
br...@google.com
wa...@gmail.com
This sounds like a bug. Can you put together a reproduction sample on github? Once I have a repro case engineering will have a look at it. Thanks!
ga...@google.com
i have the same issue with 1.13.0, when using the GMSMapViewDelegate - (UIView *)mapView:(GMSMapView *)mapView markerInfoWindow:(GMSMarker *)marker returning a custom UIView.
wa...@gmail.com
dg@ could you please post a repro case to github, I'm interested to see a full working sample. Thanks!
ga...@google.com
The below git repo contains the code that the issue occurs.
Note that If I reverse the Google Map API version to 1.12.3, the code works fine.
https://github.com/benba5/IssueGoogleMap1.13.0
Thank you very much
^__^
Note that If I reverse the Google Map API version to 1.12.3, the code works fine.
Thank you very much
^__^
tw...@gmail.com
Thanks for the repro benlbenl5!
tw...@gmail.com
We have a work around for this issue. Add the following code to the custom info window:
override func didMoveToSuperview() {
superview?.autoresizesSubviews = false;
}
override func didMoveToSuperview() {
superview?.autoresizesSubviews = false;
}
br...@google.com
Please let us know what Apple would like us to do to work around this issue, as the fix you submitted is how we have fixed this issue in the past. If they want a different fix this time, that'd be useful to know.
Thanks!
Thanks!
tw...@gmail.com
deleted
br...@google.com
Thank you so much. It works.
However, I found the new problem which is the info window disappear unexpectedly.
The scenario is that
- Click a marker to display an info window
- Click the empty area on the map
- The info window disappear unexpectedly.
Note that the info window is expected to display because I have a code to set the selectedMarker of mapview if user click an empty area.
It seems to me that setting selectedMarker doesn't work sometimes
The git for reproducing the issue
https://github.com/benba5/IssueGoogleMap1.13.0/tree/investigate_infowindow
Thank you very much
However, I found the new problem which is the info window disappear unexpectedly.
The scenario is that
- Click a marker to display an info window
- Click the empty area on the map
- The info window disappear unexpectedly.
Note that the info window is expected to display because I have a code to set the selectedMarker of mapview if user click an empty area.
It seems to me that setting selectedMarker doesn't work sometimes
The git for reproducing the issue
Thank you very much
tw...@gmail.com
@benlbenl, please raise a new issue for the new bug. Thanks!
tw...@gmail.com
Hello,
Does the old version of GoogleMaps SDK contains this selector?
I'm wondering if I can use the old version as a workaround until the new version releases.
Does the old version of GoogleMaps SDK contains this selector?
I'm wondering if I can use the old version as a workaround until the new version releases.
br...@google.com
Do me a favour and hold for about a day, mmmk?
br...@google.com
This bug has been fixed in version 1.13.1. Thanks for the reports!
tw...@gmail.com
I'll give it a try, I'll keep update informations for you.
Thank you very much!
Thank you very much!
nk...@gmail.com
So.. any luck with this solution?
tw...@gmail.com
App is still In-Review, the third day.. :/
tw...@gmail.com
The problem was solved! Passed Apple's app review.
Thank you for supporting!
Thank you for supporting!
br...@google.com
Thanks for the report!
Description
But this time I got rejected by Apple, and they say I'm using non-public selector in my app.
The selector is called `imageWithName`
First, I use Xcode to search if there is any class using this method, result shows none.
Then, I use `grep -r imageWithName`, the result shows GoogleMaps is using the selector
I'm using CocoaPods to install GoogleMaps, and the version is `1.13.0`
Previous successful submission is using 1.13.0, too.
So I'm wondering if this is a bug caused by Apple or Google Maps,
Operating system version: iOS8, iOS9
Google Maps SDK for iOS version: 1.13.0
Hardware model: iPhone6s
*********************************************************
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.
*********************************************************