macOS notification clicks do not route to the target message #3509

Activity

1. Dhaiwat10

   added

   bugSomething isn't workingSomething isn't working

   on Jul 29, 2026
2. iroiro147 commented on Jul 31, 2026

   

   iroiro147

   on Jul 31, 2026

   Contributor

   More actions

   Plan to take this. The reporter's diagnosis (macOS backend drops the extra metadata, so the click action can't carry the target) matches what I'm seeing in desktop/src/features/notifications/lib/desktop.ts — the plugin's onAction JS callback is Linux-proven, and on macOS we never get the target back into the router.

   I'll extend the existing native-notification bridge (already used on Linux for exactly this) to carry the target through the same native-notification-activated event on macOS, keeping the window-focus path frontend-owned, with a regression test covering the click→route round-trip. PR to follow against main shortly.
3. iroiro147 commented on Jul 31, 2026

   

   iroiro147

   on Jul 31, 2026

   Contributor

   More actions

   Taking this one. The reporter's diagnosis is right: on macOS the Tauri notification plugin's JS-side onAction never delivers the extra metadata back, so the router never learns the click target.

   The Linux path already solves exactly this with a backend wait_for_action that re-emits the opaque target over native-notification-activated; the frontend just focuses the window when it arrives. I'll extend that same bridge to macOS (target already travels as an opaque JSON value through the show_native_notification command), add a regression test that pins the click→target round-trip, and open a PR against main. ETA shortly.
4. iroiro147 commented on Jul 31, 2026

   

   iroiro147

   on Jul 31, 2026

   Contributor

   More actions

   Correction: I missed PR #3510 (#3510, by @Dhaiwat10) during the initial census; it already covers this scope — macOS native-notification bridge, target routing, Cargo changes, and a regression test. I'm standing down and will not open a duplicate PR. My earlier claim/intent comments on this issue should be disregarded.
5. wesbillman

   added 5 commits that reference this issue on Aug 20, 2026

   fix(desktop): route macOS notification clicks even when reveal hangs …

   ...

   872d189

   fix(desktop): force notification click navigation past same-href check

   ...

   bbc9435

   fix(desktop): route macOS notification clicks even when reveal hangs …

   ...

   8d6e525

   fix(desktop): force notification click navigation past same-href check

   ...

   10094b7

   fix(desktop): sender names in notifications + macOS click-through rou…

   ...

   4e3c9e6
6. BradGroux

   added a commit that references this issue on Aug 23, 2026

   fix(desktop): sender names in notifications + macOS click-through rou…

   ...

   71be207
7. abipalli

   added a commit that references this issue on Oct 7, 2026

   fix(desktop): sender names in notifications + macOS click-through rou…

   ...

   aae5b9d