Notifications
Push, local alerts, preferences, and activity
Alerts arrive by two different routes. Local notifications are raised by detection on your own device; push notifications come from the server for Crew, Journey, timer, and SOS events. The in-app activity feed records what happened either way.
Three things must agree before an alert appears: the feature's own setting, system notification permission, and a working delivery path. Turning a preference on does not grant the OS permission, and the OS can suppress a notification it was given.
Location-driven alerts add a fourth dependency. Zone crossings and Marker arrivals need the background location pipeline, which requires Always access and runs when the OS schedules it; force-quitting stops ordinary background updates.
Remote delivery needs a valid push path. A missing push token or unconfigured server delivery prevents a notification that every setting in the app says should have arrived.
Because of that chain, a missing alert is diagnosed rather than guessed at: check the object's own setting, then system permission, then Always location for anything location-driven, then connectivity, and finally the in-app activity feed, which records the event even when nothing appeared on the lock screen.
How to Manage STALKR Alerts
Open Settings → Safety & Alerts → Alert Preferences to change supported Zone, arrival, SOS, and Crew activity notifications. System notification permission still controls whether alerts can appear.
Why a Notification Did Not Appear
A notification needs the relevant feature setting, OS permission, a valid local or push path, connectivity for remote events, and permission for background execution where location detection is involved.