In my console logs I keep getting this error. [Error]: Invalid size is used for setting the map view, fall back to the default size{64, 64}. I am not quite sure how to deal with it or if I even need to deal with it. Any insight would be most welcome.
1 Answer 1
I kept seeing:
[mapbox-maps-flutter] [Error]: Invalid size is used for setting the map view, fall back to the default size{64, 64}.
but wasn’t sure if I needed to fix it. First, I wanted to confirm that Flutter was actually giving the map a correct, non-zero size. Here’s what I did:
Wrapped my MapWidget in a LayoutBuilder to print out the constraints Flutter is passing:
@override
Widget build(BuildContext context) {
return LayoutBuilder(
builder: (ctx, constraints) {
debugPrint('MapboxMapView constraints: '
'maxWidth=${constraints.maxWidth}, maxHeight=${constraints.maxHeight}');
return SizedBox(
width: constraints.maxWidth,
height: constraints.maxHeight,
child: MapWidget(...), // The actual Mapbox widget
);
},
);
}
Checked the console logs to see if Flutter was giving the map a ×ばつ0 layout or a real size. In my case, I saw:
flutter: MapboxMapView constraints: maxWidth=393.0, maxHeight=764.0
That meant Flutter was correctly assigning ×ばつ764.
Why the "invalid size" message might still appear:
The Mapbox iOS SDK can initially see ×ばつ0 during an early layout pass (or if contentScaleFactor doesn’t match). It logs that error and defaults to ×ばつ64 momentarily.
On the next frame, Flutter’s layout is finalized at ×ばつ764, and the map actually resizes to fill the screen.
In other words, it’s often just a harmless one-time log.
If your map ends up full-size on-screen, you can safely ignore the log. Or you can:
Upgrade to the latest
mapbox_maps_flutter/ Mapbox iOS SDK (>= 11.3.0), which is more lenient.Patch the SDK code to remove the fallback log (not recommended for production unless absolutely necessary). Similar to here: https://github.com/mapbox/mapbox-maps-ios/issues/2154