PAwR about IOS

RE: PAwR about IOS

Pallavi Patil — Mon, 06 Jul 2026 10:19:26 GMT

Hie Liu,

To help us understand the problem better, can you please provide answers for the following:
1. What extended parameters are you using? Are you trying to advertise on the coded PHY and receive this from iOS? Do you need extended advertising for the phone connection?
2. Which IOS version and iphone did you use?
3. Can you please include a sniffer capture of scenario or a sample so we can reproduce the issue at our end.

Please let us know if you have any other questions.

Best Regards

Pallavi

RE: PAwR about IOS

Nathan — Mon, 06 Jul 2026 01:37:37 GMT

Dear Pallavi，

Thanks for your reply.The current phenomenon：

Using 54 DK to simultaneously open legacy and PAwR, with legacy connected to the phone and PAwR connected to the sensor, Android can search for and pair with the device for data transmission. However, IOS system cannot even see the device, and the same goes for using the ncs app.

Please have the development team at Nordics confirm this for me.

Thanks

RE: PAwR about IOS

Pallavi Patil — Fri, 03 Jul 2026 11:11:17 GMT

Hie Liu,

Can you please clarify if your iOS device is not able to identify the correct bluetooth connected device. PaWR is not supported on IOS device but you should be able to see the bluetooth device connected atleast. Can you please check if it is visible in nrf connect for mobile.

I have also raised your query to the development team at Nordics. Can you please describe your task so we can support you better.

Best Regards

Pallavi

RE: PAwR about IOS

Nathan — Thu, 02 Jul 2026 04:38:22 GMT

Dear lan，

Thanks for your reply.

RE: PAwR about IOS

Nathan — Thu, 02 Jul 2026 04:36:52 GMT

Dear Pallavi，

Thanks for your reply.

RE: PAwR about IOS

Ian01 — Thu, 02 Jul 2026 01:08:53 GMT

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.

RE: PAwR about IOS

Pallavi Patil — Wed, 01 Jul 2026 12:01:29 GMT

Hie,

As far as I am aware, IOS prevents some apps from performing continuous active full system scans which is necessary to support PAwR. Can you please try disabling "background app refresh" in your phone and retry making the connection.

Please feel free to reach out if you have any more questions.

Best Regards

Pallavi

RE: PAwR about IOS

Nathan — Wed, 01 Jul 2026 03:03:09 GMT

Can you help me confirm this? Thank you very much