According to Android vitals there are NullPointerExceptions in com.reactnativecommunity.geolocation.PlayServicesLocationManager$2.onLocationResult
Happens mostly in Android 16 and therefore problem increases all the time as Android 16 market share increases.
geolocation-library is not well maintained, but there seems to be patch for this michalchudziak/react-native-geolocation#357 (comment)
According to Android vitals there are
NullPointerExceptionsin com.reactnativecommunity.geolocation.PlayServicesLocationManager$2.onLocationResultHappens mostly in Android 16 and therefore problem increases all the time as Android 16 market share increases.
geolocation-library is not well maintained, but there seems to be patch for this michalchudziak/react-native-geolocation#357 (comment)