Skip to content

Pushes with no link cannot be tapped #1284

Description

@johnpooch

Goal

Give every push somewhere to land, or record why it has nowhere to go.

Current behaviour

CivilDisorderSpec and CivilDisorderRecoverySpec return None from get_link(). game_deleted is emitted without a game, so render sets both link and data to None.

Both tap handlers read a link and no-op without one: the service worker reads data.FCM_MSG.data.link, and the native handler reads data.link. Tapping any of these three notifications does nothing.

Expected behaviour

Tapping a notification opens something relevant to it. Where there is genuinely nowhere to go — game_deleted names a game that no longer exists — that is recorded as a deliberate exception rather than left as an unset default.

Where

service/notification/registry.pyCivilDisorderSpec.get_link, CivilDisorderRecoverySpec.get_link, and the context.game is None branch in NotificationSpec.render; tap handling in packages/web/public/firebase-messaging-sw.js and packages/web/src/messaging-native.ts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions