All Devices How is it possible that badges...

[PastaPrimav]

...are still not cleared/updated when a notification is cleared?

I’ve read the notification. I’ve cleared it. There is no reason why a badge with a #1 still appears on the app icon until I open the app.

Manually clearing a notification should be more than enough to trigger a background app refresh event.

 

[JPack]

It's a beta.

 

[symphony]

File a bag report.

 

[TheSkywalker77]

Welcome to beta testing, my friend.

 

[PastaPrimav]

Jesus christ is that the only thing some of you know how to say?

This issue has existed since the beginning of iOS Notifications. It is relevant to iOS 13 only in the sense that still in iOS 13 there is no relationship between dismissing/clearing a banner and badge count updating.

 

[chabig]

I’ve read the notification. I’ve cleared it. There is no reason why a badge with a #1 still appears on the app icon until I open the app.

Badges don't mean that you have notifications, nor do they go away after you view the notification. They mean that there is something in the app that is asking for your attention.

 

[PastaPrimav]

Badges don't mean that you have notifications, nor do they go away after you view the notification. They mean that there is something in the app that is asking for your attention.

That is not correct. Badges correspond directly to notifications in almost all apps that use notifications, and have since the beginning.

If I receive a banner, a badge is added. I can tap on that banner to go to the event in the app, which will clear the badge because the app was opened (and the event addressed).

But if I dismiss that banner, this should serve as sufficient instruction that the event has been acknowledged. Currently it does not, and I am forced to open the app in order to acknowledge the event, and thus clear the badge.

 

[TheSkywalker77]

That is not correct. Badges correspond directly to notifications in almost all apps that use notifications, and have since the beginning.

If I receive a banner, a badge is added. I can tap on that banner to go to the event in the app, which will clear the badge because the app was opened (and the event addressed).

But if I dismiss that banner, this should serve as sufficient instruction that the event has been acknowledged. Currently it does not, and I am forced to open the app in order to acknowledge the event, and thus clear the badge.

But it is a beta bug, you said the issue started on iOS 13 and I haven’t been experiencing it, therefore it’s most likely a bug.

 

[PastaPrimav]

It's a beta.

This is not a bug, and has nothing to do with the beta.

 

[bradbomb]

That is not correct. Badges correspond directly to notifications in almost all apps that use notifications, and have since the beginning.

If I receive a banner, a badge is added. I can tap on that banner to go to the event in the app, which will clear the badge because the app was opened (and the event addressed).

But if I dismiss that banner, this should serve as sufficient instruction that the event has been acknowledged. Currently it does not, and I am forced to open the app in order to acknowledge the event, and thus clear the badge.

Badges do not always correspond to notifications. Example 1, the mail badge is there and you have the options to get notified or not when mail comes in. Example 2, if you have the Facebook App, I believe its default setting is that the badge will have a number if someone likes a post of yours, but you do not receive a notification when that happens.

Badge and notification behavior is App Specific. For instance, if you interact with a text in a notification (like reply to it), the badge that you have an unread text disappears because Messages app treats that notification interaction as if you read the text.