On Google map sdk 1.13.0, the delegate method to custom markerInfoWindow make application not resonse [35828292]

Fixed

Bug

Status Update

No update yet.

Description

be...@gmail.com

created issue #1

Mar 31, 2016 12:51PM

I develop the application with Swift, and I use Google Map SDK 1.13.0.
After update the Google Map SDK to 1.13.0, my application doesn't response when trying to show a custom marker info window.

func mapView(mapView: GMSMapView, markerInfoWindow marker: GMSMarker) -> UIView? {
let resources = NSBundle.mainBundle().loadNibNamed("CustomPopup", owner: self, options:nil) as Array
let infowindow = resources.first as! SelectionPopup
return infowindow
}

After commenting out the above method, my application become response on the mention scenario

Note that my code works on version 1.12.3

Thank you

Comments

br...@google.com <br...@google.com> #2Apr 1, 2016 04:19AM

when you are saying When I create an emulator, there is no cutout hole. It appears as I use it. I tried removing it in various ways, but the same phenomenon occurs.

Could you please tell us more about how you create your AVD? Are you creating your own skin? Or did you select one of the Device proposed in the Device Manager ? (e.g. "Small Phone", "Medium Phone", "Pixel 8",...)

there is no cutout hole. It appears as I use it

We are not sure about the situation you are referring to. Some screenshots would be useful, and also a detailed description of "It appears as I use it".

Thanks

dg...@conit.ag <dg...@conit.ag> #3Apr 4, 2016 10:10AM

Hi
Android Studio Meerkat | 2024.3.1

Pixel 9 Pro XL
Android 16.0("Baklava") | x86_64
Api: 36

======================================================================
-- AppData\Local\Android\Sdk\skins\pixel_9_pro_xl\layout

parts {
device {
display {
width 1344
height 2992
x 0
y 0
corner_radius 0 <--------------- no effect
}
}
portrait {
background {
image back.webp
}
foreground {
mask mask.webp
cutout 0 <------------------------ Deleting or changing it has no effect
}
}
}
layouts {
portrait {
width 1466
height 3101
event EV_SW:0:1
part1 {
name portrait
x 0
y 0
}
part2 {
name device
x 57
y 56
}
}
}

-- No Effect
==========================================================

The same problem occurred when using different APIs on different devices.

But after deleting all
AppData\Roaming\Google\AndroidStudio...
directories and restarting, it seems to have been resolved.

Best regards

br...@google.com <br...@google.com> #4Apr 5, 2016 12:18AM

Cutout hole appears again. I attatch a screenshot.

be...@gmail.com <be...@gmail.com> #5Apr 5, 2016 01:40AM

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
^__^

br...@google.com <br...@google.com> #6Apr 5, 2016 01:59AM

Accepted by br...@google.com.

Thanks for the repro benlbenl5!

br...@google.com <br...@google.com> #7Apr 11, 2016 12:37AM

We have a work around for this issue. Add the following code to the custom info window:

override func didMoveToSuperview() {
superview?.autoresizesSubviews = false;
}

ph...@gmail.com <ph...@gmail.com> #9Apr 20, 2016 06:11PM

Comment has been deleted.

Message last modified on May 7, 2021 04:21AM

be...@gmail.com <be...@gmail.com> #10Apr 28, 2016 07:57AM

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

br...@google.com <br...@google.com> #11May 1, 2016 12:39AM

@benlbenl, please raise a new issue for the new bug. Thanks!

br...@google.com <br...@google.com> #14May 3, 2016 12:37AM

Marked as fixed.

This bug has been fixed in version 1.13.1. Thanks for the reports!