Bluer error: GATT services have not been resolved for that Bluetooth device: Could not find service UUID on scanned device

[LeanderK]

I want to send a file from ios to linux. On ios it says: Started Bluetooth Advertisment, waiting for receiving device.

On linux it says:

Removed device 67:7B:A5:18:47:81
Using discovery filter:
DiscoveryFilter {
    uuids: {
        a70bf3ca-f708-4314-8a0e-5e37c259be5c,
    },
    rssi: None,
    pathloss: None,
    transport: Auto,
    duplicate_data: false,
    discoverable: false,
    pattern: None,
    _non_exhaustive: (),
}


Discovering on Bluetooth adapter hci0 with address 7C:21:4A:0D:2A:B8

Discovered device AC:12:2F:24:37:B3 with service UUIDs {0000110b-0000-1000-8000-00805f9b34fb, 0000110e-0000-1000-8000-00805f9b34fb, 0000111e-0000-1000-8000-00805f9b34fb, 00001800-0000-1000-8000-00805f9b34fb, 00001801-0000-1000-8000-00805f9b34fb, 86868686-8686-8686-8686-868686868686, 00001101-0000-1000-8000-00805f9b34fb, 0000110d-0000-1000-8000-00805f9b34fb, 0000110c-0000-1000-8000-00805f9b34fb, 66666666-6666-6666-6666-666666666666, 011cf5da-0000-1000-8000-00805f9b34fb}
    Manufacturer data: None
    Device failed: GATT services have not been resolved for that Bluetooth device: Could not find service UUID on scanned device
Could not establish Bluetooth connection: Bluer error: GATT services have not been resolved for that Bluetooth device: Could not find service UUID on scanned device

Removed device AC:12:2F:24:37:B3

[LeanderK]

I have compiled FlyingCarpet myself as I am currently stuck on Ubuntu 22

[spieglt]

Hmm, I've seen this with Linux receiving from macOS but not so much from iOS. Have you tried unpairing both devices from each other before starting Flying Carpet?

[spieglt]

Similar to the bug with macOS, you might also try manually initiating pairing from the iOS device in the system menu before starting Flying Carpet on each device. This will require setting the Linux device to advertise/be discoverable. If that doesn't work either, you can turn off Bluetooth in Flying Carpet and it will fall back to the QR code method.

[LeanderK]

Hmm I got this to work by chance and now I can't reproduce the steps :D

but I wonder if it tries to connect to the wrong device? When I start FlyingCarpet with the app closed on my phone, and also bluetooth disabled, it still gives me the error.

I am not connected to anything on my laptop, but in an office setting, so there are other bluetooth devices over which I don't have control. Maybe it tries to connect to the wrong one all the time, until I got lucky once?

I would try to debug it but I don't know any rust...maybe on a weekend I'll try to do something.

[spieglt]

Strange. It does seem like it's connecting to the wrong device, but it's only supposed to discover devices advertising the Flying Carpet service UUID. But that service UUID isn't in the ones listed for the discovered device.... I'm not sure, I'll think about it. Anything else above those logs on Linux?

[LeanderK]

no, it's the console output. Any more logs to provide?

[LeanderK]

Interestingly, there's a new development: It now tries to connect but I can't accept it on my phone, the bluetooth connection request just keeps popping up and up and up and up, but I can not push the "pair" button the next one is popping up. Maybe a timeout for the pairing request is set too low (not the overall)?

My log looks like this:

Processed other event: PropertyChanged(Discovering(true))
Discovered device 46:AF:19:17:23:74 with service UUIDs {a70bf3ca-f708-4314-8a0e-5e37c259be5c}
    Manufacturer data: None
    Device provides our service!
    Connecting...
    Connected
    Service UUID: d0611e78-bbb4-4591-a5f8-487910ae4366
    Service data: [Primary(true), Uuid(d0611e78-bbb4-4591-a5f8-487910ae4366), Includes([])]
    Service UUID: 89d3502b-0f36-433a-8ef4-c502ad55f8dc
    Service data: [Primary(true), Uuid(89d3502b-0f36-433a-8ef4-c502ad55f8dc), Includes([])]
    Service UUID: 0000180f-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(0000180f-0000-1000-8000-00805f9b34fb), Includes([])]
    Service UUID: 9fa480e0-4967-4542-9390-d343dc5d04ae
    Service data: [Primary(true), Uuid(9fa480e0-4967-4542-9390-d343dc5d04ae), Includes([])]
    Service UUID: a70bf3ca-f708-4314-8a0e-5e37c259be5c
    Service data: [Primary(true), Uuid(a70bf3ca-f708-4314-8a0e-5e37c259be5c), Includes([])]
    Found our service!
    Characteristic UUID: e1fa8f66-cf88-4572-9527-d5125a2e0762
    Characteristic data: [Uuid(e1fa8f66-cf88-4572-9527-d5125a2e0762), Notifying(false), Flags(CharacteristicFlags { broadcast: false, read: true, write_without_response: false, write: true, notify: true, indicate: false, authenticated_signed_writes: false, extended_properties: true, reliable_write: true, writable_auxiliaries: false, encrypt_read: false, encrypt_write: false, encrypt_authenticated_read: false, encrypt_authenticated_write: false, secure_read: false, secure_write: false, authorize: false }), CachedValue([]), Mtu(512)]
found password characteristic
    Characteristic UUID: bee14848-cc55-4fde-8e9d-2e0f9ec45946
    Characteristic data: [Uuid(bee14848-cc55-4fde-8e9d-2e0f9ec45946), Notifying(false), Flags(CharacteristicFlags { broadcast: false, read: true, write_without_response: false, write: true, notify: true, indicate: false, authenticated_signed_writes: false, extended_properties: true, reliable_write: true, writable_auxiliaries: false, encrypt_read: false, encrypt_write: false, encrypt_authenticated_read: false, encrypt_authenticated_write: false, secure_read: false, secure_write: false, authorize: false }), CachedValue([]), Mtu(512)]
found OS characteristic
    Characteristic UUID: 0d820768-a329-4ed4-8f53-bdf364edac75
    Characteristic data: [Uuid(0d820768-a329-4ed4-8f53-bdf364edac75), Notifying(false), Flags(CharacteristicFlags { broadcast: false, read: true, write_without_response: false, write: true, notify: true, indicate: false, authenticated_signed_writes: false, extended_properties: true, reliable_write: true, writable_auxiliaries: false, encrypt_read: false, encrypt_write: false, encrypt_authenticated_read: false, encrypt_authenticated_write: false, secure_read: false, secure_write: false, authorize: false }), CachedValue([]), Mtu(512)]
found ssid characteristic
    Service UUID: 00001805-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(00001805-0000-1000-8000-00805f9b34fb), Includes([])]
    Service UUID: 00001801-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(00001801-0000-1000-8000-00805f9b34fb), Includes([])]
    Service UUID: 7905f431-b5ce-4e99-a40f-4b1e122d00d0
    Service data: [Primary(true), Uuid(7905f431-b5ce-4e99-a40f-4b1e122d00d0), Includes([])]
    Service UUID: 0000180a-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(0000180a-0000-1000-8000-00805f9b34fb), Includes([])]

Only after not being able to connect it logs:

Could not establish Bluetooth connection: Bluer error: internal error: D-Bus error org.freedesktop.DBus.Error.Timeout: Timeout waiting for reply

[spieglt]

Apologies for the delay but I'm pretty stumped by this one. Apple-to-Linux has been a particularly buggy and difficult part of the Bluetooth work. I'm working on some changes to ensure that Linux and Windows devices don't write the WiFi information over Bluetooth until they've actually stood up their hotspots, so the other device doesn't try to join too early and have to retry. If I run into issues like this as I test and develop that, I'll let you know.

[LeanderK]

thanks, please ping me in case there's something to try!

[UlyssesZh]

Same error on Linux (receiving file from Windows).

Using discovery filter:
DiscoveryFilter {
    uuids: {
        a70bf3ca-f708-4314-8a0e-5e37c259be5c,
    },
    rssi: None,
    pathloss: None,
    transport: Auto,
    duplicate_data: false,
    discoverable: false,
    pattern: None,
    _non_exhaustive: (),
}


Discovering on Bluetooth adapter hci0 with address 48:68:4A:8F:04:52

Discovered device 64:35:D8:7F:52:24 with service UUIDs {}
    Manufacturer data: Some({4c: [10, 6, 4d, 1d, 76, fe, 26, 18]})
    Device failed: GATT services have not been resolved for that Bluetooth device: Could not find service UUID on scanned device
Could not establish Bluetooth connection: Bluer error: GATT services have not been resolved for that Bluetooth device: Could not find service UUID on scanned device

Removed device 64:35:D8:7F:52:24

[spieglt]

@UlyssesZh Have you tried manually unpairing the devices in their Bluetooth settings and running Flying Carpet again?

[UlyssesZh]

Yes.

[Zyx-A]

我也遇到了这个问题。

Discovering on Bluetooth adapter hci0 with address 2C:9C:58:xx:xx:xx

Processed other event: PropertyChanged(Discovering(true))
Discovered device 5D:D1:38:xx:xx:xx with service UUIDs {a70bf3ca-f708-4314-8a0e-5e37c259be5c}
    Manufacturer data: None
    Device provides our service!
    Connecting...
    Connected
    Service UUID: 00001801-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(00001801-0000-1000-8000-00805f9b34fb), Includes([])]
    Service UUID: 0000fe35-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(0000fe35-0000-1000-8000-00805f9b34fb), Includes([])]
    Service UUID: 11c8b310-80e4-4276-afc0-f81590b2177f
    Service data: [Primary(true), Uuid(11c8b310-80e4-4276-afc0-f81590b2177f), Includes([])]
    Service UUID: 0000046a-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(0000046a-0000-1000-8000-00805f9b34fb), Includes([])]
    Device failed: GATT services have not been resolved for that Bluetooth device: Did not read all Flying Carpet characteristics from peer.
Could not establish Bluetooth connection: Bluer error: GATT services have not been resolved for that Bluetooth device: Did not read all Flying Carpet characteristics from peer.
SSID flyingCarpet_1e86 was not a known network
Removed device 5D:D1:38:xx:xx:xx
Using discovery filter:
DiscoveryFilter {
    uuids: {
        a70bf3ca-f708-4314-8a0e-5e37c259be5c,
    },
    rssi: None,
    pathloss: None,
    transport: Auto,
    duplicate_data: false,
    discoverable: false,
    pattern: None,
    _non_exhaustive: (),
}


Discovering on Bluetooth adapter hci0 with address 2C:9C:58:xx:xx:xx

Processed other event: PropertyChanged(Discovering(true))
Discovered device 54:3D:D3:xx:xx:xx with service UUIDs {a70bf3ca-f708-4314-8a0e-5e37c259be5c}
    Manufacturer data: None
    Device provides our service!
    Connecting...
    Connected
    Service UUID: 11c8b310-80e4-4276-afc0-f81590b2177f
    Service data: [Primary(true), Uuid(11c8b310-80e4-4276-afc0-f81590b2177f), Includes([])]
    Service UUID: 00001801-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(00001801-0000-1000-8000-00805f9b34fb), Includes([])]
    Service UUID: 0000fe35-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(0000fe35-0000-1000-8000-00805f9b34fb), Includes([])]
    Service UUID: 0000046a-0000-1000-8000-00805f9b34fb
    Service data: [Primary(true), Uuid(0000046a-0000-1000-8000-00805f9b34fb), Includes([])]
    Device failed: GATT services have not been resolved for that Bluetooth device: Did not read all Flying Carpet characteristics from peer.
Could not establish Bluetooth connection: Bluer error: GATT services have not been resolved for that Bluetooth device: Did not read all Flying Carpet characteristics from peer.
SSID flyingCarpet_1e86 was not a known network
Removed device 54:3D:D3:xx:xx:xx

[spieglt]

@Zyx-A Could you post the output from the other side? This is also with an iOS device?