Edit history

Earlier versions of Push notifications stop after presence transitions to offline (iOS PWA backgrounded), newest first.

Current version | Edited by Rex
Changes
- Client: iOS Safari, installed as Home Screen PWARemoved: ### Logs or screenshotsRemoved: Removed: _No response_Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched existing issues.Removed: - ☑ I wrote this report in my own words, except for direct translation if needed.Removed:
Show

Push notifications stop after presence transitions to offline (iOS PWA backgrounded)

Summary

On a self-hosted instance, push notifications work correctly while the iOS PWA is foregrounded and the user's presence is online. However, once the app is backgrounded and presence automatically transitions to offline (the normal/expected behavior after a few seconds), push notifications stop arriving entirely even though the push subscription remains valid and registered.

Steps to reproduce

  1. Install Fluxer as a PWA on iOS via Safari's "Add to Home Screen."
  2. Open the app, grant notification permission, confirm status shows online.
  3. Send a test message from another account/device while the PWA is open to confirm the notification arrives.
  4. Background the PWA (swipe up / leave the app) without force-quitting it.
  5. Wait a few seconds for presence to visibly transition from online to offline (confirmed via another client).
  6. Send a message from a separate account/device.

Environment

  • Self-hosted instance (Docker Compose deployment)
  • Client: iOS Safari, installed as Home Screen PWA
Original by Rex
Show

Push notifications stop after presence transitions to offline (iOS PWA backgrounded)

Summary

On a self-hosted instance, push notifications work correctly while the iOS PWA is foregrounded and the user's presence is online. However, once the app is backgrounded and presence automatically transitions to offline (the normal/expected behavior after a few seconds), push notifications stop arriving entirely even though the push subscription remains valid and registered.

Steps to reproduce

  1. Install Fluxer as a PWA on iOS via Safari's "Add to Home Screen."
  2. Open the app, grant notification permission, confirm status shows online.
  3. Send a test message from another account/device while the PWA is open to confirm the notification arrives.
  4. Background the PWA (swipe up / leave the app) without force-quitting it.
  5. Wait a few seconds for presence to visibly transition from online to offline (confirmed via another client).
  6. Send a message from a separate account/device.

Environment

  • Self-hosted instance (Docker Compose deployment)
  • Client: iOS Safari, installed as Home Screen PWA

Logs or screenshots

No response

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.