-
Notifications
You must be signed in to change notification settings - Fork 836
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
Library detecting AltBeacons but not iBeacons #1223
Comments
I haven't worked with AltBeacon, but I worked with iBeacons. The library follows the approuch how it is designed on iOS where we gave Region that we need to monitor. I didn't see that you called BeaconManager.startMonitoring(region). It's important for iBeacon I support it's enought to call startRaning to find AltBeacon. Check this one first:
Then: And finally: |
@VolodaUa Thank you for getting back to me! I took a look and tried to play around a bit but I can still only detect an AltBeacon. The below log shows what I get for the AltBeacon.
Through the BeaconScope app I grabbed the raw packet of the beacon I am emitting which is below
I tried this exact template Any ideas or issues with what you see below? If it were a
|
@vinceprofeta Have you checked the reference app? Is it works there? |
@VolodaUa I will have to try it out. My code mirrors the java code in the reference app, and the reference app is using a really old version of Gradle, and not building. ill have to dig in.
It may be worth noting that from the logs It appears to see the right packet with uuid |
@VolodaUa the Kotlin version of the reference applicaiton detect the beacon but the Java application does not. |
Okay update. I rewrote it in KT following the reference app exactly. I can still only detect AltBeacons
|
Please specify the UUID of the beacon in your region Region( |
@VolodaUa I've tried that, confirmed in the logs, confirmed the right parser was being used. Altbeacons work fine, and I see the packet in the logs but they are getting filtered out. I've feel like I have exhausted all potential solutions without digging into the core of this library... Im not sure if there is an issue with the RN bridge or context where there is some override happening or a parsing issue. |
@vinceprofeta focus on iBeacons first and specify region. Not sure that library will support two types of beacons at the same time. When you start monitoring , please also add request StateForRegion to get didDetermibateState callback with region state and start ranging if you are inside. |
@VolodaUa thank you. Sorry I was out. Can you be a bit more clear what you mean by I have tried every combination of beacon parser. single, multiple, clearing, not clearing, etc. |
I would suggest moving this issue to StackOverflow and closing it here. BeaconManager.requestStateForRegion() function. I would suggest call it when you request to start monitoring beacons. beaconManager.startMonitoring(region) MonitorNotifierImpl.kt
override fun didDetermineStateForRegion(state: Int, region: Region) {
|
I'm developing a React Native module that uses the AltBeacon library to scan for iBeacons. While the implementation successfully detects AltBeacons, it's not detecting any iBeacons.
I am emitting beacons from BeaconScope on both Android and iOS. I am certainly doing something simple wrong, but would love some help.
https://github.com/vinceprofeta/react-native-beacon-radar/blob/main/android/src/main/java/com/beaconradar/BeaconRadarModule.java
Current Implementation:
What's Working:
didRangeBeaconsInRegion
methodWhat's Not Working:
Things I've Tried:
Questions:
Environment:
Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: