Info window: tns-core-modules/ui/utils doesn't have a _layoutRootView method anymore

[logangeorge01]

In map-view.ios.js the mapViewMarkerInfoContents function calls tns-core-modules/ui/utils ios._layoutRootView which does not exist in tns anymore as of pull request #7382 on June 25. I don't know whether this breaks all info windows or just custom ones, but it's throwing this error and crashing the app.

JavaScript error:
file:///node_modules/nativescript-google-maps-sdk/map-view.js:164:30 JS ERROR TypeError: webpack_require("../node_modules/tns-core-modules/ui/utils.js").ios._layoutRootView is not a function. (In 'webpack_require("../node_modules/tns-core-modules/ui/utils.js").ios._layoutRootView(content, CGRectMake(0, 0, width, height))', 'webpack_require("../node_modules/tns-core-modules/ui/utils.js").ios._layoutRootView' is undefined)

[EmielH]

I'm having the same problem. Looking at the pull request, this broke from Nativescript 6. Apparently the method was already deprecated, see here. The commit doesn't mention an alternative, unfortunately.

This basically means it's impossible to use infowindows on iOS when using Nativescript 6.

[logangeorge01]

Thanks. We decided to use an infowindow not tied to the map, which works way better than Google Maps' anyways. It's an actual component now, so we can do data binding and actually call functions.

[EmielH]

@logangeorge01, could you please reopen this issue? I'm glad to see that you have found an alternative solution, but I (and probably other people as well) would like to keep using the map's infowindows. The bug in this library has not been solved yet. Thanks a lot!

[dlcole]

I have the same issue, and agree with @EmielH . I gather the new approach is not yet available, as the code, demo, and readme have not been changed recently. What alternatives do we have?

[logangeorge01]

We decided to create a custom info window component that we show/hide based on marker tap. It allows for a LOT more customizability than the hacky Google Maps info window.

[EmielH]

I'm afraid we may have to go that way as well, as there doesn't seem to be any activity in this repo, and unfortunately I currently don't have the knowledge to fix this bug myself.

[dlcole]

For folks following along at home, see my SO post for a manual hot fix that works.