Troubleshooting
Direct checks for common field problems
Most field problems are a scope problem, a permission problem, or a delivery problem, and they look identical on the map. Checking which Crew is selected first resolves more of them than any other single step, because objects and members belong to one Crew and were never global.
STALKR keeps failure states distinct rather than tidy. A Crew list that could not be fetched is reported as unavailable rather than as an empty account, a delivery warning means writes are not reaching the Crew even though the device has a fix, and a stale marker is labelled as the last known point rather than drawn as current.
Nothing is replayed after a failure. Because remote writes are not queued, a Track that would not start, a Marker that would not save, and an SOS that could not reach the service are failures rather than delayed successes — retrying is the recovery, not waiting.
For anything location-driven, work down the chain in order: the object's own setting, system permission at the level the workflow needs, whether the app was force-quit, GPS accuracy, and connectivity.
Why STALKR Says Crew List Unavailable
STALKR could not confirm your Crew memberships. It preserves the difference between a failed fetch and having no Crews, so it does not falsely show an empty account.
Why a Crew Member Is Missing or Stale
The person may be in another Crew, Dark, without permission, offline, out of battery, or unable to reach STALKR. A stale marker is only the last known point.
Why a Zone Alert Did Not Fire
The Zone needs monitoring plus the relevant Enter/Leave toggle, a real transition after baseline priming, usable GPS accuracy, background permission/execution, notifications, and any required connectivity.
Why Direction Is Not Updating
STALKR omits or steadies the heading when the compass fix is invalid or noisy. Move away from magnetic interference and calibrate the phone with a figure-eight motion.
Why a Route Is Not Visible
The global Routes & Checkpoints layer or that Route’s Show on map setting may be off, or its geometry may not have loaded. An actively followed Route is the intentional exception and stays visible.
Why You Cannot Move a Marker
Marker movement requires edit authority, the dedicated Move action, a hold-and-drag gesture, and a successful save. Another map tool can also block the move.
Why Background Location Is Not Working
Always location may be denied, the app may have been force-quit, the OS may have suspended execution, or the current build still needs device-specific validation.
Why a Profile Photo Is Missing
The upload may have failed, the remote URL may be unavailable, or STALKR may have suppressed a failed image. Retry from Edit Profile with connectivity; the prior avatar remains authoritative until a save succeeds.
Why a Track Will Not Start
Starting a Track creates its server row before recording, so you must be signed in and connected. A Track cannot currently be started as a fully offline local recording.
Why You Cannot Go Dark
The selected Crew may have Tracking Enforced. The Live/Dark control cannot bypass that rule; an authorized owner must disable enforcement in Crew settings.