PAwR about IOS

Hi Nordic team,

Does IOS currently not support PAwR?

I am currently using the NCS version: v3.3.1 by 54L15 DK.When I open both extended broadcast and PAwR, BLE Sniffer(PC)and Android can see the device, but IOS cannot.

I saw someone mention the same issue in DevZone before, but there was no solution.

unable to see extended advertising on IOS (15/17 with IOD 26.x) with nrfConnect/SI Connect or Nano Connect - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

Is this a problem caused by IOS's features and mechanism?

Thanks and regards.

Parents
  • iOS may have Bluetooth hardware support internally, but third-party apps cannot use PAwR through public CoreBluetooth APIs. CoreBluetooth exposes the normal BLE app model: scan for advertising peripherals, connect, discover GATT services and characteristics, read, write, notify, indicate, and advertise limited GATT-related data as a peripheral. Apple’s CBCentralManager documentation describes scanning, discovering, and connecting to advertising peripherals, and CBPeripheralManager is centered around publishing GATT services and advertising them to centrals.

    Apple’s public peripheral advertising API is also limited. CBPeripheralManager.startAdvertising(_:) only accepts normal advertising data, and Apple documents that the peripheral manager supports only CBAdvertisementDataLocalNameKey and CBAdvertisementDataServiceUUIDsKey for advertising data. That is far below the level of control required for Extended Advertising or PAwR.

    Bluetooth - CI Tracker is focused on standard BLE and GATT debugging on iPhone. It helps developers, firmware engineers, hardware teams, and testers scan nearby BLE peripherals, inspect GATT services and characteristics, send custom Hex commands, enable notifications, configure reusable Profiles, build data parsers, set timers and receive rules, and inspect live TX / RX / SYSTEM / PARSE / ERROR logs.

Reply
  • iOS may have Bluetooth hardware support internally, but third-party apps cannot use PAwR through public CoreBluetooth APIs. CoreBluetooth exposes the normal BLE app model: scan for advertising peripherals, connect, discover GATT services and characteristics, read, write, notify, indicate, and advertise limited GATT-related data as a peripheral. Apple’s CBCentralManager documentation describes scanning, discovering, and connecting to advertising peripherals, and CBPeripheralManager is centered around publishing GATT services and advertising them to centrals.

    Apple’s public peripheral advertising API is also limited. CBPeripheralManager.startAdvertising(_:) only accepts normal advertising data, and Apple documents that the peripheral manager supports only CBAdvertisementDataLocalNameKey and CBAdvertisementDataServiceUUIDsKey for advertising data. That is far below the level of control required for Extended Advertising or PAwR.

    Bluetooth - CI Tracker is focused on standard BLE and GATT debugging on iPhone. It helps developers, firmware engineers, hardware teams, and testers scan nearby BLE peripherals, inspect GATT services and characteristics, send custom Hex commands, enable notifications, configure reusable Profiles, build data parsers, set timers and receive rules, and inspect live TX / RX / SYSTEM / PARSE / ERROR logs.

Children
Related