transistorsoft / react-native-background-geolocation

Sophisticated, battery-conscious background-geolocation with motion-detection
http://shop.transistorsoft.com/pages/react-native-background-geolocation
MIT License
2.64k stars 425 forks source link

Financial apps and ACCESS_FINE_LOCATION #2172

Open UnderTheMoonspell opened 1 week ago

UnderTheMoonspell commented 1 week ago

So according to new Google guidelines (https://support.google.com/googleplay/android-developer/answer/9876821?hl=en), EWA apps, like ours, are forbidden to have Access_fine_location permission, which has made them first blocking our app in review, and lately they even removed our app from the play store (without any warning). So we had to remove both permissions and hide the feature that uses this lib to have the app approved (still pending so we've been two days without the app on the store). While this process is ongoing, I was trying to do some testing with the app requesting only Access_coarse_location. The app seems to work fine, difference being theres no precise option in Android when the modal shows up, until it eventually always crashes with an ANR.

image

I'm wondering why the precise location should be a requirement for the lib to work, but its a fact, that if I use the two permissions the app works as usual.

Your Environment

Expected Behavior

Actual Behavior

Steps to Reproduce

  1. Open the app
  2. Give location permissions
  3. Wait

Context

Debug logs

Logs ``` PASTE_YOUR_LOGS_HERE ```
jdlourenco commented 1 day ago

Hi @christocracy is this behavior expected? We've been unable to use the library in our apps due to the ACCESS_FINE_LOCATION permission requirement. Despite the potential impact on accuracy we would like to experiment using the library without requiring it, is this something that should be possible?