Not a LatLng or LatLngLiteral

Question

Uncaught ge {message: 'not a LatLng or LatLngLiteral: in property lat: not a number', name: 'InvalidValueError', stack: 'Error\n    at new ge (https://maps.googleapis.com/m…tp://localhost:3001/static/js/bundle.js:82399:27)

The latitude and longitude are numbers only, still getting this error.

Please provide a [mcve] that demonstrates your issue. – geocodezip Feb 19 '22 at 15:51 — geocodezip, Feb 19 '22 at 15:51

score 0 · Accepted Answer · answered Feb 19 '22 at 23:09

The most recent release added validation in a couple locations that catches some invalid duck typing of LatLng.

Likely you are passing an object somewhere that has .lat() and .lng() but is not a LatLng or a subclass of LatLng. This is invalid.

Instead you should pass a LatLngLiteral with an object have lat and lng properties and number values.

Not a LatLng or LatLngLiteral

1 Answers1