Closed JB-CHAUVIN closed 1 month ago
I quickly googled this. It seems like we can avoid this by adding a declaration that we do not use the location when we scan Bluetooth.
https://developer.android.com/develop/connectivity/bluetooth/bt-permissions
I'm currently on my phone. Can you add this assertion in your app to see if that works? Otherwise we might need to change the package.
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.BLUETOOTH_SCAN" tools:remove="android:usesPermissionFlags" />
<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" tools:remove="maxSdkVersion" />
Fixed the issue !
Description: I am experiencing an issue with the react-native-flic2 library in my React Native project on Android. When I include the react-native-flic2 library and request location permissions, the app requests only approximate location of the device. However, when I do not include this library, the app requests precise & approximate location permission (desired behaviour).
Steps to Reproduce:
Expected Behavior: The app should request the same location permissions regardless of whether the react-native-flic2 library is included or not.
Actual Behavior:
With react-native-flic2 library: The app requests approximate location permission.
Without react-native-flic2 library: The app requests approximate AND PRECISE location permission.
Environment: React Native version: 0.74.3 react-native-flic2 version:0.3.26 react-native-permissions: 4.1.5 Android version: Android 14 Device: Samsung Target Android SDK : 34