-
Notifications
You must be signed in to change notification settings - Fork 451
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
Secure UUID enter/exit area detection is erroneous in random situation #124
Comments
@maddie Yup, we already had identified this problem and will be issuing fix within next release. I'll keep this issue open till release is ready. |
@wiktor Good to know! Thanks for your great work! |
Should be fixed with v0.9.2. |
Same thing still happening with v0.9.3 The monitoring runs in a Service. Still randomly checks in/out... |
@wiktor Thanks. But with the very same code, only changing Region to SecureRegion, random onEnter/onExit still occurs.. Only when I use Region the problem seems to go away. This happened on Nexus 5 and OnePlus Two, both running Lollipop. |
@maddie Can you enable debug logging in the SDK ( |
Log as below, that's all I can get with As the trigger seems to be another beacon around the device (not owned by me, of course), I have used an iPhone as a Virtual Beacon (using the Estimote app). Once I turned it on, seconds later the device registered the onEnter event. After turning the virtual beacon off, the device calls onExit. The application was running on a Nexus 5, with stock Android 5.1
|
Any thoughts? |
Does this problem still appear with the latest SDK? We've implemented some Secure UUID and monitoring improvements since 0.9.1. |
Hi @heypiotr , Thanks for the response. Actually the log above was from using v0.9.4. I'm not sure if I can provide any more logs to troubleshoot the problem. It occurs on Nexus 5, OnePlus Two, and Xiaomi 4, so I guess it shouldn't be hardware related. |
The application I'm developing is an auto check in/out application, which will monitor the only one beacon that I've owned. I have updated to 0.9.1 and enabled Secure UUID as per the updated README.
At first it seems like it works just fine, however when I leave the area of my own beacon and went to some other places, my application still triggers onEnter and onExit, like it was entering my beacon's area.
This was not the case when I haven't enabled Secure UUID on previous versions of the SDK.
I'm not sure how could I provide any logs since it occurs quite randomly in what it appears to be in random locations.
And I've noticed that these events were triggered like I was really entering my beacon's area, for example, when I enter a mall (which likely have beacons), it checks in. When I leave its proximity, it checks out.
The text was updated successfully, but these errors were encountered: