Ramon
Thanks for reporting this issue. Indeed, Google Play Services has introduces a breaking change. See release notes here: https://developers.google.com/android/guides/releases#october_13_2022 As you already mentioned please keep using Google Play Services Location...
Have the Gradle custom plugins been tested? (e.g. SDK Registry one)
Hi thanks for reporting this issue. We'll look into it. Meanwhile, you can workaround it by setting bearing to the default value `FollowPuckViewportStateBearing.SyncWithLocationPuck` instead of `null`: ```Kotlin viewportPlugin.transitionTo( viewportPlugin.makeFollowPuckViewportState( FollowPuckViewportStateOptions.Builder()...
Thanks @TeeKoo for your report. We will take a look and report back.
The code in this repo is a mirror of the internal one. Please @ThibaudLopez open the PR to the internal one.
Thanks @ivoGanev for your detailed report. We'll investigate it further and report back.
@alingocab Have you released an app with [crashlytics 18.3.0](https://firebase.google.com/support/release-notes/android#crashlytics_v18-3-0) (or higher) recently?
Thanks, [Crashlytics release 18.3.0](https://firebase.google.com/support/release-notes/android#crashlytics_v18-3-0) introduced this change that might explain why you see it more often: > Improved crash reporting reliability for crashes that occur early in the app's lifecycle
This issue has been resolved in [v10.10.0](https://github.com/mapbox/mapbox-maps-android/releases/tag/v10.10.0). It's now possible to use Google Play Services Location 20 or 21.