Mbed-os: Homekit ADK accessory with iPhone 8 and iPhone X with 5.12.0 mbed

Created on 12 Mar 2019  Â·  7Comments  Â·  Source: ARMmbed/mbed-os


Hi,
HomeKit ADK disconnects immediately when we try with iPhone8 or iPhone X with iOS version 12.1.4 (16D57) when using 5.12.0 of mbed
However Homekit ADK works fine with same iPhone8 and iPhoneX with iOS version 12.1.4 (16D57) with mbedOS version 5.11.4.

There seems to be lot of changes in the Cordio stack between 5.11.4 and 5.12.0. Is there any additional API needs to be taken care in latest Cordio Stack.

Additional Info:
Homekit ADK works fine with iPhone 7 with iOS version 10.3.1 (14E304) and iPhone5s with iOS version 12.1.4 with mbed version 5.12.0

Issue request type


[ ] Question
[ ] Enhancement
[x ] Bug

CLOSED mirrored bug

Most helpful comment

With this fix the issue is solved

All 7 comments

Would it be okay to share the sniffer trace of disconnecting scenario? Thanks.

sniffer.zip
failure case sniffer log

We are also facing similar issue with GattServer example app,
Logs from GattServer with iphone X + iOS-12.1.4

Starting GattServer
Ble process started.
Ble instance initialized
Advertising started.
Adding demo service
clock service registered
service handle: 11
hour characteristic value handle 13
minute characteristic value handle 16
second characteristic value handle 19
Connected.
-- end of log

Usecase: BLE_GattServer + iPhoneX (iOS 12.1.4) with LightBlue app

  • iphoneX able to discover the GattServer device via LightBlue app
  • tap to connect GattServer device
  • On iPhone side it is showing “connecting” -> “Interrogating” then pop up message “Connection Alert” Timeout.
  • No disconnection or any other logs from serial console, It appears the stack just hanged after this

From the trace, the communication is gone after phy_update_ind, so I think all examples have the same issue, and that’s why iPhone 7 doesn’t has the issue because it’s bt4.2.

Hi @akhilcypress I just raise a PR #10092 for this, could you check if this solve your issue? Thanks.

With this fix the issue is solved

Was this page helpful?
0 / 5 - 0 ratings

Related issues

neilt6 picture neilt6  Â·  4Comments

ccchang12 picture ccchang12  Â·  4Comments

bcostm picture bcostm  Â·  4Comments

sarahmarshy picture sarahmarshy  Â·  4Comments

hasnainvirk picture hasnainvirk  Â·  3Comments