Creating and destroying multiple maps causing other maps to throw PlatformException(channel-error, Unable to establish connection on channel., null, null) about mapbox-maps-flutter HOT 5 CLOSED

@LjubiTech-Maxko @dawid-niedzwiecki I assume it's related to the multimap setup and #54, looking as well.

from mapbox-maps-flutter.

Same issue here, pushing one view with a map on top of another view with a map, it raises that exception.

May I ask when this issue is estimated to be resolved?

In the meantime - are there any known workarounds?

from mapbox-maps-flutter.

Probably related because styleLayerExists is called on the second instance of the map which is at the time of calling already disposed.

from mapbox-maps-flutter.

This doesn't seem to be fixed.
Map 1 initialises without issues.
Map 2 initialises, then we destroy it later.
Back on map1, any methods run on its MapboxMap instance throws:
PlatformException(channel-error, Unable to establish connection on channel., null, null)

Seems the second map's instance is somehow bound to the first map's MapboxMap instance now.

Miraculously the first map is still able to function despite these exceptions. So it's as if it's bound to two maps at the same time.

from mapbox-maps-flutter.

Just an update on our issue. We have a home screen with a map and I noticed the whole map widget rebuilds each time we pop the navigation stack back home.
Since it was rebuilding and we often move the map based on actions done on child pages, it was trying to run these methods on an old instance of the map controller.

This is unfortunate, that the map is rebuilt entirely.

We made a hack where we save a reference to the map widget the first time it's built, then return this map variable each time the build is retriggered, instead of allowing it to rebuild each time.

from mapbox-maps-flutter.