The mesh message notifications don't seem to work. I can't make them appear to test, and when I do see one and click "view message" it doesn't take me to that message.
As well, read messages seem to go to unread after a while or with a refresh of the page, not consistent. Will log.
Steps to Reproduce
Msg a node.
Usually notification appears.
Expected Behavior
Notification box appears and is clickable to read the message and respond
Actual Behavior
Notification doesn't appear or does not take you to the message.
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
### Description
The mesh message notifications don't seem to work. I can't make them appear to test, and when I do see one and click "view message" it doesn't take me to that message.
As well, read messages seem to go to unread after a while or with a refresh of the page, not consistent. Will log.
### Steps to Reproduce
Msg a node.
Usually notification appears.
### Expected Behavior
Notification box appears and is clickable to read the message and respond
### Actual Behavior
Notification doesn't appear or does not take you to the message.
### Archipelago Version
1.7.99-alpha
### Hardware
x86_64 (Intel/AMD)
### Relevant Logs
_No response_
### Screenshots
_No response_
App-wide notifications now poll the actual radio-mesh queue (Meshtastic, MeshCore, and Reticulum), not only federation messages.
A single-message toast deep-links to the exact contact conversation.
Read state uses the durable per-contact highest-seen message ID, so refreshes cannot turn old history into “11 unread”.
Fixed the empty-history edge case that swallowed the first message on a new node.
Corrupt persisted read state now recovers safely.
Verification: frontend type-check/build green; full Vitest suite green (118 files, 1007 tests), including new refresh-persistence and first-message notification coverage.
Fixed in `a624d11b` and pushed to `main`.
- App-wide notifications now poll the actual radio-mesh queue (Meshtastic, MeshCore, and Reticulum), not only federation messages.
- A single-message toast deep-links to the exact contact conversation.
- Read state uses the durable per-contact highest-seen message ID, so refreshes cannot turn old history into “11 unread”.
- Fixed the empty-history edge case that swallowed the first message on a new node.
- Corrupt persisted read state now recovers safely.
Verification: frontend type-check/build green; full Vitest suite green (118 files, 1007 tests), including new refresh-persistence and first-message notification coverage.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
The mesh message notifications don't seem to work. I can't make them appear to test, and when I do see one and click "view message" it doesn't take me to that message.
As well, read messages seem to go to unread after a while or with a refresh of the page, not consistent. Will log.
Steps to Reproduce
Msg a node.
Usually notification appears.
Expected Behavior
Notification box appears and is clickable to read the message and respond
Actual Behavior
Notification doesn't appear or does not take you to the message.
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
I got one new message and it went to 11
These were all previously read
Fixed in
a624d11band pushed tomain.Verification: frontend type-check/build green; full Vitest suite green (118 files, 1007 tests), including new refresh-persistence and first-message notification coverage.