window.google object is gone after unmount and mount the Lazy-loading Wrapper Component.

I don’t really sure why. When the component is unmounted, the window.google is still. But, when the wrapper component is mounted again, the window.google becomes null for unknown reason. I look through the implementation of wrapper and found that the ScriptCache.js loads the Google map script only once and no hope to reload it even if the window.google object is gone away from browser. The solution I’ve temporally did is to recreate my own wrapper with this add-on function.

componentWillUnmount() {
  window._scriptMap.delete("google");
}

However, I don’t think it is a good idea to do so. Could you figure out why the window.google object is gone when remounting and fix it?

[codewithcats]

It seems like window.google is reset every time. My current workaround is make a change in GoogleApi: from

let google = window.google == null;

to

let google = window.google || null;

[Szarko]

I believe I might be facing a similar issue, I have a component on Page A that runs my map component using this module. When navigating to a link to Page B and coming back to Page A the map does not load as the google prop is set to null.

I notice the .loaded is still true though.

Is this what you are describing?

In the documentation when the author describes manually loading the window.google instance, I am not sure what he is referring to. I wonder if using this manual loading would be an alternative solution.