I agree with PBK's thoughts. Should not increment the badge count if there is no way to reset that on the server level, it literally provides no benefit.

If you have removed the ability to reset the badge count on the server side (whats sent in thr payload), then you should also remove the server keeping track of the badge count (so that everytime a notification is delivered, the payload is 1 for badge count). For my simple app it is not an acceptable solution to create an entire extension just to ensure the badge count shown is not the sum of all cloudkit notifications ever received.

Hi, so to confirm if using subscriptions for notifications on cloudkit, i would have to manually alter the badge number shown? This really seems like an oversight, why would cloudkit continue to keep track of the badge number but then not allow me to reset it? I would much rather cloudkit didnt keep track of the badge count if its not going to allow me to clear it?