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
When I run my App (SwiftUI code shown below) an error: Generic(value: "the device did not transmit a central client uuid")
The EUDI wallet always goes into peripheral mode and thus it will not provide a central client uuid. It would appear that the mobile-sdk-swift implementation assumes that it will be the peripheral.
Am I understanding things correctly? Is there a plan to support Central mode for the MdocReader?
<key>NSBluetoothAlwaysUsageDescription</key>
<string>Secure transmission of mobile DL data</string>
I never see a prompt asking for permission for BlueTooth.
The app's settings does not show a switch for BlueTooth.
I expect that the app never prompts for permission because it fails parsing the URI from the qrCode and never actually attempts bluetooth communications.
The text was updated successfully, but these errors were encountered:
Are the MdocReader and related Ble and BleConnection classes intended to support the creation of an mdL Verifier on iOS?
I have attempted to get this working by scanning a QR code presented by the EUDI wallet. Here is an example of what the EUDI wallet QR code provides:
When I run my App (SwiftUI code shown below) an error:
Generic(value: "the device did not transmit a central client uuid")
The EUDI wallet always goes into peripheral mode and thus it will not provide a central client uuid. It would appear that the mobile-sdk-swift implementation assumes that it will be the peripheral.
Am I understanding things correctly? Is there a plan to support Central mode for the MdocReader?
My App's Info.plist file has:
I never see a prompt asking for permission for BlueTooth.
The app's settings does not show a switch for BlueTooth.
I expect that the app never prompts for permission because it fails parsing the URI from the qrCode and never actually attempts bluetooth communications.
The text was updated successfully, but these errors were encountered: