• just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    6 days ago

    Clever. Not much you can do for this except not subscribe your app to the notifications API, or take extra steps to attempt to clear them, but I don’t remember that being an option on iOS. Going to be an interesting fix.

      • evasive_chimpanzee@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        ·
        6 days ago

        I’m assuming that changes what it actually displays, but is there confirmation that those data dont enter the notification system on the back end?

      • just_another_person@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        6 days ago

        This is for the client display only, and not the iOS API interface as I’m discussing. It’s not very plainly laid out in the docs, but one would assume any queuing of content into the notification system would be stored or cached if not cleared. There doesn’t seem to be a way to have a client of that system to clear it’s own data once it’s in there, just cancel last notification.