Iftekhar Rifat
Iftekhar Rifat
You're using java 18, that's probably causing the issue. RN recommends to use jdk 11
Sorry for the late reply, unfortunately I don't think I completely understand the problem you described. Can you please provide a scenario that's causing the issue ?
So the main issue is that AppState change is being triggered when location dialog pops up. So it's difficult to figure out if the app is actually in background, am...
Can't think of a good solution for this. If we use lifecycle listener in native side, they'll also get triggered when showing location popup. I'll think on this, and see...
Sure, let me know if you have any suggestion.
You can use [react-native-background-fetch](https://github.com/transistorsoft/react-native-background-fetch) library to execute task in background.
Not by default, you have to use some kind of work scheduler to request location in background. `react-native-background-fetch` should do the trick as far as I know.
`forceRequestLocation` ony kicks in when user selects `No` from location dialog. You're not showing the location dialog, that's why it's bailing out early with that error.
Setting `showLocationDialog: true` should fix the issue.
`showLocationDialog` is needed not only for enabling gps, but also to enable location service if it's disabled. So you need to set this to true. You can set this to...