After a prolonged BLE connection, we have noticed that ANCS frequently pushes a large number of "remove" messages (event ID 0x02), after which the device no longer receives any notifications. Is this behavior a result of system design, or could it be a potential bug? I would appreciate any insights or experiences that others can share.
Are these "remove" messages coming for notifications that have been read or cleared from the Notification Center on the phone? If so, that would be expected.
Also, when the device is not receiving the notifications, is your accessory still connected, or able to see the advertisements for the ANCS service? Because, as stated in Apple Notification Center Service (ANCS) Specification "ANCS is not guaranteed to always be present"
If you are getting "remove" messages for unread/undeleted notifications, and notifications are no longer arriving despite the ANCS service seemingly being available, our engineering teams would need to investigate this issue, as this might indicate an issue with iOS.
If that is the case, we'd greatly appreciate it if you could open a bug report, include crash logs and sample code or models that reproduce the issue, and post the FB number here once you do.
It would be very helpful if you could please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for iOS to install a logging profile on your device. Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. And attach that to the Feedback report as well.
Bug Reporting: How and Why? has tips on creating a successful bug report.
Argun Tekant / DTS Engineer / Core Technologies