Notifications

When FCM is configured, technicians may see assignment created/removed, rescheduled, or cancelled notices. Foreground banner copy can fall back to A job was updated. Sync to refresh.

Notification ≠ synchronization authority. Always confirm Sync.

App states

App state	What happens
Open (foreground)	In-app banner and a sync request
Background	OS may show the system notification. Tap → session → sync → job if cached
Force-killed / terminated	Local queued work stays on disk. Sync does not continue. OS may still deliver FCM; tap opens the app

Logged out: a tap cannot open a job until someone signs in. Android 13+ asks for notifications once after a Field session (not on the login screen). If the technician denies permission, jobs still sync when the app is open.

Workspace mismatch: This notification is for another workspace. Switch workspace to open it.

Missing cache: This job is not available offline.

No unsupported killed-app periodic sync claim. There is no background message handler. Revoking push does not wipe local work.

Manifest already declares POST_NOTIFICATIONS and a default FCM channel field_jobs. See Firebase.