-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No beacons detected when ranging and phone locked Android #141
Comments
I suppose Android Oreo has put forth execution limits in the background, as well as when the app is killed. In order to continuously(regardless of the state) detect beacons, you need a foreground service. Which device are you using? Share the logs from Android Studio, that could show when detection was stopped. |
我遇到了同样的问题,请问您解决了吗 |
@27comar Hey did you get any further with this issue? I don't see any foreground service being managed in the library's android code. |
I encountered the same problem before, you try to modify the version of react-native |
@chentianci123 I am using version 0.59.10 of react-native |
You changed the react-native version of react-native-beacons-manager to be the same as your version, or integrated the source code of this plugin directly into your existing project |
@sfreeman28 @chentianci123 I'm really sorry, I wasn't active on my GitHub account until now. In fact, in the Hope this helps :) |
Thank you @27comar! Yes this solves the issue, thanks for the reply =] |
Hi @sfreeman28, I'm happy I could help you ! |
Version
1.0.7
Platform
Android
OS version
Android 8.1.0
Steps to reproduce
Expected behavior
The beacons around should be visible in the array of the 'beaconsDidRange' event, like when the app is in foreground.
Actual behavior
The 'beaconsDidRange' event is triggered each second, but the array of beacons around is empty.
When the app is in foreground or background but the phone is unlocked, the ranging works correctly. The only problem is when the phone is locked. I only have access to a 8.1.0 Android device, so I couldn't test with other versions.
The text was updated successfully, but these errors were encountered: