regiseloi-idlab
commented
2 days ago For reference, Device engagement using QR code is defined in section 8.2.2.3 of the 18013-5 spec.
Open regiseloi-idlab opened 2 days ago
regiseloi-idlab
commented
2 days ago For reference, Device engagement using QR code is defined in section 8.2.2.3 of the 18013-5 spec.
In testing with a wallet other than Orbit, we've been unable to complete the bluetooth pairing step. It's unclear whether the issue is with the QR code presented by the wallet or the way it's been read and handled.
Steps to reproduce:
Expected result: scan of nearby bluetooth device shows the device that was used to generate the QR code. Actual results: 1) if using Orbit, the device shows up as "My Device" regardless of what the device is actually called, but it works. 2) if using the EUDI or Scytales ID, the connection fails right away with
Bluetooth connection failed, please reconnect!2a) in the background, it appears to retry to connect, which is not going to work. 2b) in the console, the error is:Bluetooth connection failed TypeError: Failed to execute 'requestDevice' on 'Bluetooth': Invalid Service name: '������E4�����xO�'. It must be a valid UUID alias (e.g. 0x1234), UUID (lowercase hex characters e.g. '00001234-0000-1000-8000-00805f9b34fb'), or recognized standard name from https://www.bluetooth.com/specifications/gatt/services e.g. 'alert_notification'.