-
-
Notifications
You must be signed in to change notification settings - Fork 308
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
ConnectToKnownDeviceAsync is giving null as device name #834
Comments
I'm the friendly issue checker. If you think it's fine to make an exception, just ignore this message. Thanks! |
This might be related to #541, right? Although that one was reported for iOS, they might have a common origin (in particular if the issue is due to DiscoveredDeviceRegistry, as suspected). |
Once BLE device is connected, I remember GUID. Next time when user opens up, I am trying to connect to that device using ConnectToKnownDeviceAsync.
When I used
ConnectToKnownDeviceAsync
to connect to device, it is giving me a null for the device name in Android 14 devices.Expected behavior
Device name should come just like ConnectToDeviceAsync or Advertisement is giving.
Actual behavior
In case of connection made using
ConnectToKnownDeviceAsync
is not giving device name in Android 14 devices.Crashlog
It is not causing any crash in library.
Configuration
Version of the Plugin: 3.1.0-beta.3
Platform: Android 14
Device: Google Pixel 7a
The text was updated successfully, but these errors were encountered: