WristviaCheck the source notification first, then permissions, source choices, connection and watch presentation. A phone “sent” entry or Apple push acceptance is not proof of a visible wrist alert.
1. Did the phone show an eligible notification?
Check the source app on Android. If it posted no eligible notification, Wristvia has nothing to forward. Source-app settings and Android notification permission are separate from Wristvia notification access.
2. Can Wristvia access and forward that source?
In Android settings, check Wristvia’s notification access. In Wristvia, check the source selection, global pause, per-app temporary mute and preview choices. A generic alert may be intentional privacy behavior rather than missing text.
Use the app’s background-delivery guidance for your phone. An earlier unplugged overnight gap remains unresolved; a battery exemption alone does not prove reliability.
3. Are you nearby, or using Internet Backup?
Nearby Bluetooth and Internet Backup have separate states. Open Connection on both devices. A saved link is not proof of a current transport connection. For apart-device delivery, backup must be enabled with approval on both devices and both ends must have internet.
If backup says off or needs attention despite previous approval, use Connection’s existing retry/check flow. Do not erase the link or unpair Apple Watch as a first step. A recent service contact proves authenticated access, not alert presentation.
4. What did the watch actually do?
Check notification permission, Focus/silent settings, preview privacy and the Wristvia inbox. A saved preview, visible card, sound and haptic are separate observations. An expired or cancelled preview may no longer be readable or available for catch-up.
A short-look Wristvia icon is expected because watchOS identifies the delivering app. The source icon belongs inside the detailed alert when available and privacy allows it.
5. Record a useful report
Note the app versions, phone/watch models, time, nearby versus apart, whether the phone was locked/unplugged and what each screen actually showed. Avoid personal notification text, QR codes, push tokens and keys. Contact Wristvia and review the known gaps.
Will it work all day with the phone locked?
There is no qualified all-day guarantee or measured battery saving. An earlier unplugged overnight notification gap remains unresolved; background Health activity is a separate observation. Android power management, watch wake opportunities, range and permissions can each affect results.
Test a known notification with the phone locked and unplugged, then a longer idle period, and record actual wrist presentation and battery use. Do not assume a battery exemption or successful desk test completes that qualification. See the background and battery answer.