You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked the documentation and FAQ without finding a solution
I checked to make sure that this issue has not already been filed
Expected Behavior
When a non-null array of UUID strings is passed to startDeviceScan(), any device with any of the passed UUIDs should be scanned, both on iOS and on Android
Current Behavior
In versions > 2.0.3 I see scan results from some UUIDs, but not all on Android i.e. devices with some UUIDs are missing when scanned from Android.
The issue does not occur on IOS, and does not occur at all with v2.0.3
Library version
3.1.2
Device
Android 12 OnePlus Nord N20 5G CPH2459
Environment info
Using react-native v0.72.6 indirectly through expo v0.10.16
Steps to reproduce
let theBleManager = new BleManager(bleManagerOptions);
Issue seems to be specific to Eddystone UUID 0000feaa-0000-1000-8000-00805f9b34fb so replacing this issue with more specific issue [#1155], which includes link to repository with minimal reproducible example.
Prerequisites
Expected Behavior
When a non-null array of UUID strings is passed to startDeviceScan(), any device with any of the passed UUIDs should be scanned, both on iOS and on Android
Current Behavior
In versions
> 2.0.3
I see scan results from some UUIDs, but not all on Android i.e. devices with some UUIDs are missing when scanned from Android.The issue does not occur on IOS, and does not occur at all with
v2.0.3
Library version
3.1.2
Device
Android 12 OnePlus Nord N20 5G CPH2459
Environment info
Steps to reproduce
let theBleManager = new BleManager(bleManagerOptions);
theBleManager.startDeviceScan([ "uuid1", "uuid2", ...], null, callback);
Formatted code sample or link to a repository
I have not created the sample repository in case the included information might be enough.
Is it ok to submit a minimal runnable expo repository to illustrate the issue?
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: