Bart Louwers

I tried to reproduce this in our test app. No luck so far... https://github.com/maplibre/maplibre-native/commit/3cf9a8ea9aceb79b8b6edca09f1d0556378e4297  @westnordost Can you try removing the expressions which use logarithms?

@westnordost Could you try reproducing it with https://github.com/maplibre/maplibre-native/commit/3cf9a8ea9aceb79b8b6edca09f1d0556378e4297 ?

Sure I can do that! Looks device specific. No problem on Samsung S10 with LineageOS (Android 12). 

Oh really, interesting! Please leave a comment if someone sees it again. cc @TimSylvester @alasram

@dakuenne Any chance you can share the style? That will help us look into this.

To look into this we something we can test on our development machines. An ideal reproduction is a style with embedded GeoJSON sources we it does not rely on a...

I would be very reluctant to accept any contributions from people who have contributed to our even seen Mapbox' proprietary codebase. That said, if someone writes a piece of code...

Here maybe? https://github.com/maplibre/maplibre-native/blob/bf40cdf5f73403d9855d02a10fdf5eba0a43cbe0/platform/android/MapLibreAndroid/src/main/java/org/maplibre/android/location/LocationCameraController.java#L317

Makes sense. That is definitely not expected behavior I think. I think it's fair to categorize this as a bugfix instead of a breaking change. PR welcome! Could you add...

Could you sort the results from `queryRenderedFeatures(coordinate: PointF, radius: Float, ...)` yourself perhaps?