Map interaction events sometimes have invalid zoom levels

[mick]

Example of a interaction event that has an invalid zoom level

  { event: 'map.click',
  created: '2016-04-21T08:59:35.688Z',
  lat: 59.34534534,
  lng: 124.345345,
  zoom: 2147483648,
  orientation: 'Portrait',
  gesture: 'Rotation',
  version: 2}

Platform: Android
Mapbox SDK version:4.2.0

Steps to trigger behavior

Not sure, doesn't happen frequently. Seen on rotations.

Expected behavior

Have the actual map zoom level

Actual behavior

Has 2147483648 as the zoom level

cc @zugaldia

[zugaldia]

Has 2147483648 as the zoom level

@mick That's interesting, the zoom level is reported as 2^31, looks like an overflow somewhere. I'll look into it.

[zugaldia]

The only place in the SDK where we build a GESTURE_ROTATION_START event is on RotateGestureListener.onRotateBegin() within MapGestureDetector. Unfortunately, I can't seem to reproduce that large zoom value after trying different styles, locations (including the one in the OP), or initial zoom states.

@mick I'll leave the ticket open for now. Meanwhile, do you want the SDK to filter out likely invalid large zoom values events?

[tobrun]

in #8767, I'm adding a MapboxEventWrapper where we have more granular control over what is getting dispatched to telemetry. This was needed to handle the issue from #8650 correctly. I'm suggesting to add some logic to this wrapper class to not send data when the zoom level is not found between max/min.