Zooming out very far causes null pointers

[lenis0012]

When zooming out very far and moving the map around, you are greeted with the following error.

https://pastebin.com/VxQ5jKhX

Setting the pan boundary to -90, -180 and 90, 180 did not resolve the issue.

[alfanhui]

That error looks like the centre MapOptions is not set. If you have your MapOptions arguments, this will help more, or try setting centre to LatLng coordinates.

The pan boundaries take LatLng coordinates at southwest and northeast boundaries, so setting them using degrees does not work (or make sense? )

[lenis0012]

Hi @alfanhui
Thanks for your response.

these are the options I am using

options: new MapOptions(
        center: new LatLng(51.5, -0.09),
        zoom: 2.0,
        swPanBoundary: new LatLng(-90.0, -180.0),
        nePanBoundary: new LatLng(90.0, 180.0),
      ),

[GregorySech]

Right now when using the package example zooming out does not cause an exception to be thrown but the map simply freezes and cannot be "zoomed in".

[raacker]

@GregorySech Did it actually freezed? After zooming out lots of times, I was still able to zoom in after bunch of zooming in... maybe we can prohibit zoom maximum at 8000KM or 15000KM?

Zooming out until 15000KM will no longer load maps and it's quite useless for normal usage :)

[raacker]

@GregorySech So far, I found that the exception is HttpException because scale is already too negative to get map image file. And when Zoom level is very close to 0, it's almost out of the whole map.

What about to stop zoom at this scale on above image by forcing zoom to be positive value? I mean never go negative.

[GregorySech]

@GregorySech Did it actually freezed? After zooming out lots of times, I was still able to zoom in after bunch of zooming in... maybe we can prohibit zoom maximum at 8000KM or 15000KM?

Zooming out until 15000KM will no longer load maps and it's quite useless for normal usage :)

Yeah, the map froze but the rest of the app was still usable. I literally just panned out on my phone and was unable to pan-in again.
Avoiding negative values might be the right move but its @johnpryan strategic decision.