Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

From Android 10 to 13 can't detect beacons #65

Open
nbastoWM opened this issue Sep 29, 2022 · 0 comments
Open

From Android 10 to 13 can't detect beacons #65

nbastoWM opened this issue Sep 29, 2022 · 0 comments

Comments

@nbastoWM
Copy link

Hi,

"react-native": "0.66.1",
"@estimote/react-native-proximity": "https://github.com/Estimote/react-native-proximity.git#13887046",

I've also tried with:
"@estimote/react-native-proximity": "^0.6.0",

Tried with and without this permissions in Manifest:

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
<uses-permission android:name="android.permission.ACCESS_BACKGROUND_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />

Also tried with and without this service in Manifest:
<service android:enabled="true" android:exported="false" android:name="com.estimote.scanning_plugin.packet_provider.service.PacketProviderWrapperService" android:foregroundServiceType="location"/>

Android location permission is detected as "always".

It can detect beacons on Android 9 but not on Android 10, 12, or 13.

With the plugin from the commit 1388704 it shows the "Exploration Mode" in the notification bar, but with the plugin version 0.6.0 it doesn't.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant