JorenVos

The promise is not resolving at all. React Native 0.66.4 / iOS15.4 ``` import { useIAP } from 'react-native-iap'; getSubscriptions(['MONTHLY']).then(() => { console.log('Done'); }).catch(() => { console.log('Error') }); ``` `Done`...

This is a UX-blocker for us in production, it's not the way we want to request permissions from our users. Is it possible to get yourself an Android 13 device...

I did a fresh install of the app from the Play Store and the first thing I see is: Notification permission request. It's in Dutch, but it's really strange that...

Followed the setup instructions to add the library to a clean project. Same behavior happens after a restart of the app. [SampleProject.zip](https://github.com/transistorsoft/react-native-background-geolocation/files/9459894/SampleProject.zip) I do not have access to the codebase...

In my opinion, it still needs a fix. `react-native-background-geolocation` should not ask for notification permissions because these are only used for debugging purposes. Everyone who's using this package and has...

It should not request the permission **before** a `config` or `init` of the library is called. The fact that this library can cause a permission request on boot is unwanted.

I'm currently dealing with exactly the same problem. When watching for location updates in the background, it's impossible to use `getCurrentPosition` in another part of the application.

> @here Any update or alternate to fix watchLocation and getCurrentPosition usage conflicts issue. I'm using https://github.com/mauron85/react-native-background-geolocation for "watchLocation" purposes as it handles background watching and https://github.com/Agontuk/react-native-geolocation-service for "getCurrentPosition" purposes....