-
Notifications
You must be signed in to change notification settings - Fork 504
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
Cannot scan Eddystone service UUID on Android with versions > 2.0.3 #1155
Comments
Contact me if you need a beacon to test this. |
Note: This problem persists with or without Could this issue be related to dotintent/MultiPlatformBleAdapter#102 ? |
The bug has been confirmed and we are working on it. |
Hi @pwellner, |
Good news, Thanks. Let me know if there's anything I can do to help. |
@EmmaZachara, Any update? I noticed this issue appears even with I'll be glad to upgrade the example |
More info: |
Hi @pwellner |
@dominik-czupryna-withintent, would you consider accepting a PR to fix this bug? I would like to fix this if you or your colleagues are open to it. To get me started, could you point me to the Android dependency repository that you think will need attention? |
Hi @pwellner, If you have any additional questions, feel free to ask, I will help if I can. |
Prerequisites
Expected Behavior
startDeviceScan(["0000feaa-0000-1000-8000-00805f9b34fb"], ...)
should find BLE devices advertising with this standard Eddystone UUID when running on iOS and on AndroidCurrent Behavior
When using
v3.1.2
devices with this UUID are NOT found on Android, but are found correctly on iOS.When using
v2.0.3
devices with this UUID are found correctly on Android AND on iOSLibrary version
3.1.2
Device
Android 12 OnePlus Nord N20 5G CPH2459
Environment info
Steps to reproduce
Connect Android device to development system with Android studio installed, and have an Eddystone beacon available nearby.
Run test program on device. Press the "GET PERMISSIONS" button, accept all permissions, then press the "SCAN SELECTED" button, and observe the log files.
Devices with Eddystone UUID
"0000feaa-0000-1000-8000-00805f9b34fb"
are not logged.Run test program again and observe the logs. Devices with Eddystone UUID
"0000feaa-0000-1000-8000-00805f9b34fb"
are all found correctly.Formatted code sample or link to a repository
https://github.com/pwellner/ble-plx-scan-bug
Relevant log output
Devices with UUID
0000feaa-0000-1000-8000-00805f9b34fb
appear correctly on iOS and on Android when usingv2.0.3
, but they do not appear when usingv3.1.2
on AndroidAdditional information
No response
The text was updated successfully, but these errors were encountered: