Hi all,
I'm encountering a BLE issue with the newer iPad models featuring the A16 Bionic chip (e.g., iPad 11th Gen). I have an iOS application that runs as a BLE peripheral, and it used to work flawlessly with various central devices.
📱 Device Specs
-
Model: iPad (A16 Bionic)
-
OS: iPadOS 18.6
✅ Working Setup (Before):
- iOS app acts as a BLE peripheral (advertises a custom service).
- Central device (Windows/Linux/Android) could:
-
- Discover advertisements
-
- Connect to the peripheral
-
- Exchange MTU
-
- Discover GATT services
-
- Communicate bidirectionally
❌ Issue with iPad A16 (Newer Devices):
-
Central device receives advertisements and connects.
-
MTU exchange request is sent by central, but iPad A16 does not respond.
-
The BLE link remains active but only transmits empty PDUs, and communication never proceeds.
-
Same issue observed with third-party apps like BLE HID keyboard — they also fail to connect or communicate on A16 iPads but work on older devices (e.g., iPad 10th Gen and below).
🔍 Debugging So Far:
-
Confirmed that MTU Exchange Request is compliant (Client Rx MTU = 527).
-
Works fine with iPad 10th Gen and earlier.
-
Works with Android, Windows, and even Linux central stacks with older iPads.
-
A16-based iPads seem to silently drop or ignore the MTU request.
🧪 Suspected Cause:
-
Possible regression or behavioral change in LE Privacy handling on newer iPads.
-
Possibly tied to iPadOS version or Bluetooth controller firmware.
🙏 Looking for:
-
Anyone else facing similar BLE issues on iPads with A16?
-
Any known changes to BLE LE Privacy, MTU negotiation, or connection behavior in iPadOS on A16 devices?
-
Any workarounds, entitlements, or configuration changes that fixed the issue?
Would appreciate any insights or suggestions. Thank you!