Save map instance

I couldn`t find a way to save google map instance so you can prevent initialization every time you change the screen, is there such a way?

[dfavaro]

I guess it's fine for the map to be initialized every time.
Why instead don't you save the informations you need in order to initialize it again based on your needs?

[arriolac]

I filed an issue on the Compose-side to support this as the current available APIs cannot, afaik, support this feature request. You can +1 https://issuetracker.google.com/issues/252891031

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

[PRO8L3M]

Any news/plans for that?

Honestly, as I wanted to migrate from fragment-based to Compose Google Maps I've encountered issue with reloading MapView (when coming back to the screen with Map). From UX perspective this is no go for that migration because of UX regression.

[kikoso]

Hi @PRO8L3M .

There is a PR that will fix this issue: #436

Since this PR was created, a new Compose version was released (1.4.0), which supports overloading onReset and onRelease in the AndroidView.

Aiming to get this merged real soon.

[philip-segerfast]

PR #436 will only allow reuse in containers which support reuse. Maybe this is achievable though depending on how the navigation is implemented etc.

[PRO8L3M]

When do you expect to merge that PR?