CoreBluetooth connection never starts

Question

Created Nov ’25

Replies 4

Boosts 0

Participants 2

I'm scanning for peripherals, and keep references to multiple CBUUIDs - one for each peripheral.

I then start a connection to the peripheral. I never get a callback to say the connection succeeded, failed, or disconnected.

I have a Mini-Moreph Bluetooth sniffer. The sniffer shows that the iPhone never tried to connect to any of the peripherals.

The iPhone HCI logs show that a create connection request was sent, but a cancel connection request was sent 0.018 seconds later. No feedback was given to my application through CoreBluetooth.

I've filed this through Feedback Assistant, but expect nothing will come of the report.

Answered by DTS Engineer in 873079022

I haven't had any other "bug number" given back to me

That FB number was what I was looking for. Thanks.

I think you should have a read of Bug Reporting: How and Why? It’s full of information about how the bug reporting process works, including info about bug numbers.

I also recommend that you read through Quinn’s Top Ten DevForums Tips. It’s my collection of hints and tips on how to use the forums effectively.

Anyway, looking at FB21100266 I see it marked as a dup of an internal bug. That bug is being investigated by the Bluetooth engineering team, but I’ve no info to share beyond that.

any suggestions of a workaround while this is fixed

I don’t know enough about Bluetooth to offer any insights into that. I’m gonna ping a colleague about it. However, if no one follows up here then you should assume that there isn’t a workaround.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

ball-hayden OP

4d

As expected, nothing has come of the report.

0

Answer 2

DTS Engineer OP

Apple

1d

What was your bug number?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 3

ball-hayden OP

1d

Thank you for your engagement @DTS Engineer

FB21100266 is the Feedback Assistant number - I haven't had any other "bug number" given back to me, if this is different?

I had an initial response to clarify the evidence I'd submitted, then nothing further.

I'm really looking for:

a) confirmation if this is a bug in iOS, so that I can pass this information to management

b) any suggestions of a workaround while this is fixed, given the massive impact this has had on our Apple customers for the last 2 months.

0

Answer 4

DTS Engineer OP

Apple

17h

Recommended

I haven't had any other "bug number" given back to me

That FB number was what I was looking for. Thanks.

I think you should have a read of Bug Reporting: How and Why? It’s full of information about how the bug reporting process works, including info about bug numbers.

I also recommend that you read through Quinn’s Top Ten DevForums Tips. It’s my collection of hints and tips on how to use the forums effectively.

Anyway, looking at FB21100266 I see it marked as a dup of an internal bug. That bug is being investigated by the Bluetooth engineering team, but I’ve no info to share beyond that.

any suggestions of a workaround while this is fixed

I don’t know enough about Bluetooth to offer any insights into that. I’m gonna ping a colleague about it. However, if no one follows up here then you should assume that there isn’t a workaround.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0