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'm the friendly issue checker.
It seems like (25.00 %) you haven't used our issue template 😢 I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message. But if you think it was a mistake to delete the template, please close the issue and create a new one.
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: