Notifications triggered on one device not appearing on another

Cross-Device Notification Sync: The Hidden Failure Points

When notifications trigger on one device but fail to appear on another, the root cause is almost never a simple “glitch.” Analysis of game economies and client-server architectures shows this pattern emerges from three specific failure points: stale token states, session priority conflicts, and push channel throttling. Understanding these mathematically is the first step to a permanent fix.

Token State Mismatch

Every device registers a unique push token with the notification service (APNs for iOS, FCM for Android). When a notification is triggered, the server sends it to the token associated with the account. If the second device’s token is expired, revoked, or not properly registered, the notification is sent to a dead endpoint. The server logs a success, but the user sees nothing.

Device State	Token Status	Notification Delivery
Fresh install, logged in	Active, registered	Delivered
App updated, token changed	Old token still stored server-side	Sent to invalid endpoint
Device offline for 30+ days	Expired by push service	Dropped silently
Multiple accounts on same device	Token overwritten by last login	Only last account receives

The fix requires a token refresh on every app launch and a server-side deduplication check. If the server does not validate token freshness before sending, the failure is baked into the architecture.

Session Priority and Device Ranking

Many game and app servers assign a priority rank to each logged-in device. The device that most recently authenticated often gets “primary session” status. Notifications are then sent only to the primary device to avoid spam. If the second device is marked as secondary or idle, it is excluded from the push queue.

Session Type	Notification Delivery	User Experience
Primary (last login)	All notifications	Expected behavior
Secondary (older session)	Silent or none	Missing alerts
Web session active	Mobile suppressed	Cross-device gap

Check your account’s active sessions list. If the missing device is listed as “inactive” or “last used 7 days ago,” the server has deprioritized it. Logging out and back in on that device forces a new primary token registration.

Push Channel Throttling and Rate Limits

Push notification services enforce rate limits per app, per device, and per topic. If the triggering event occurs rapidly, such as multiple in-game actions in one second, the server may batch or drop notifications to stay under the limit. The first device receives the batch, the second receives nothing because the batch was consumed.

Common Throttling Scenarios

• Rapid fire events: 5 notifications in 2 seconds. Server sends 3 to first device, skips second.
• Topic subscription mismatch: Second device not subscribed to the correct topic, for example “trade_offers” versus “general.”
• Cooldown per device: Some services enforce a 1-second cooldown per device token. If both tokens share the same IP or account ID, the second is delayed or dropped.

To diagnose, trigger a single, non-repeating notification, such as a manual test alert from the app’s settings. If it arrives on both devices, the issue is rate limiting. If it only arrives on one, the issue is token registration or session priority.

Operating System and Battery Optimization Interference

Modern mobile OSes aggressively manage background processes to save battery. If the app on the second device is in “optimized” or “restricted” battery mode, the push service may not wake the app to display the notification. This is especially common on Android 12 and later, as well as iOS 15 and later.

OS Setting	Effect on Push Delivery	Recommended Fix
Battery optimization: Restricted	Push delayed or blocked	Set to “Unrestricted” or “Not optimized”
Background data: Disabled	No push when app in background	Enable background data
Do Not Disturb: Scheduled	Silent notification only	Check DND schedule
App hibernation (Android)	App force-stopped, no push	Disable hibernation for this app

Go to the second device’s settings, find the app, and disable all battery optimization and background restrictions. Then force-close and reopen the app. This resets the background service state.

Server-Side Delivery Confirmation vs Client-Side Display

There is a critical distinction between the server sending a notification and the client displaying it. The server logs “delivered” when the push service accepts the payload. The client may receive it but fail to display it due to a foreground or background state conflict, a corrupted notification channel, or a missing intent handler.

Diagnostic Steps

• Enable notification logs in the app’s developer settings, if available.
• Check the device’s notification history. On Android, go to Settings, then Apps, then Special access, then Notification access.
• On iOS, check if the notification appears in the Notification Center but not as a banner. This indicates a presentation setting issue.

Probabilities do not lie. If the server sends 100 notifications and the second device displays 0, the failure is not in the server’s push logic—it is in the client’s ability to render. The expected value of a single retry is near zero. You need a systematic reset of the notification pipeline on the affected device.

Final Strategy: The Three-Step Reset Protocol

Do not waste time with random toggles. Follow this data-driven sequence:

1. Revoke and re-register tokens: Log out of the app on all devices. Clear app data on the problematic device. Log in again. This forces a fresh token registration and session priority reset.
2. Disable all battery optimization: Set the app to “Unrestricted” on Android. On iOS, ensure Background App Refresh is enabled.
3. Test with a single event: Trigger one notification manually. Verify delivery on both devices. If the second device still fails, the issue is a deep OS-level conflict or a corrupted app install. Reinstall the app.

In practice, step 1 resolves the majority of cross-device notification failures. Step 2 resolves a significant portion of the remainder. The remaining cases require a full reinstall or contacting the developer to check server-side token deduplication logic. Trust the data, not luck. If the second device never shows notifications after this protocol, the problem is architectural, not configurable. Analysis of the system for preserving notification value makes the next fix clear: demand server-side token validation and multi-device delivery support.