Hello, We are I am reviewing an app-controlled icon-badge design for my app using UNUserNotificationCenter.setBadgeCount. This is a design question, not a reported device failure. Real-device badge testing and activation remain pending. We need to understand this sequence: App process A issues a badge update but terminates before receiving its completion callback. App process B starts later, calls setBadgeCount(0), and receives successful completion. The app may subsequently set a new badge count for new activity. Could you clarify: Does process B’s successful zero update guarantee that every badge request from process A has finished or been discarded, so none can change the badge later? This includes an old zero request that could erase a newer count. When a setBadgeCount completion handler reports an error, is that particular operation finished, with no further badge-value change possible from it? We are not assuming that an error means no change occurred. If a new-process zero does not provide the guarantee in question 1, is there a supported public API to cancel outstanding badge operations or establish that all earlier operations have finished before new badge updates resume? Please identify any relevant documented guarantees and the iOS versions they cover. Our proposed design uses one coordinator for local badge writes and does not include automatic remote badge numbers. Thank you, Adrian