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.
BETA
Why STALKR Says Crew List Unavailable
Short answer
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.
Steps
Check connectivity.
Retry loading Crews.
If the issue persists, contact support with the time and incident reference if shown.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
BETA
Why a Crew Member Is Missing or Stale
Short answer
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.
Steps
Confirm you selected the same Crew.
Ask them to check Live and location permission.
Check their last-update time and connectivity.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
PARTIAL
Why a Zone Alert Did Not Fire
Short answer
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.
Steps
Open the Zone and check monitoring and Enter/Leave.
Check Always location and notifications.
Confirm you crossed the boundary after STALKR established a baseline.
Avoid force-quit during the test.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
BETA
Why Direction Is Not Updating
Short answer
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.
Steps
Hold the phone away from metal or magnets.
Move it in a figure eight.
Wait for a valid true-heading fix outdoors.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
BETA
Why a Route Is Not Visible
Short answer
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.
Steps
Open Map Layers and enable Routes & Checkpoints.
Open MANAGE ROUTES and enable that Route’s visibility.
Open the Route to load its geometry.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
BETA
Why You Cannot Move a Marker
Short answer
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.
Steps
Cancel any active map tool.
Open the Marker and choose Move.
Hold and drag, then tap SAVE.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
PARTIAL
Why Background Location Is Not Working
Short answer
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.
Steps
Check iOS Settings → STALKR → Location → Always.
Do not force-quit the app.
Verify with a physical-device field test and inspect the resulting timestamps.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
BETA
Why a Profile Photo Is Missing
Short answer
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.
Steps
Check Camera/Photo permission for the chosen source.
Retry the upload with connectivity.
If it persists, contact support with the time of the attempt.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
BETA
Why a Track Will Not Start
Short answer
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.
Steps
Check connectivity and account state.
Try START TRACK once more.
Wait for a usable GPS fix after it starts.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
BETA
Why You Cannot Go Dark
Short answer
The selected Crew may have Tracking Enforced. The Live/Dark control cannot bypass that rule; an authorized owner must disable enforcement in Crew settings.
Steps
Confirm the selected Crew.
Open Crew settings as an owner.
Disable enforced tracking, then return to GO DARK.
What happens next
The saved change appears in the relevant map, library, or sharing scope when the service confirms it.
Common problems
Check that you selected the intended Crew or Journey scope.
If the action writes data, confirm the device has connectivity and try once more.
JOIN THE BETA
Know your people are safe.
Get early access to Stalkr — real-time location awareness and safe-arrival tracking for families, travelers, and outdoor crews. One email, no spam, unsubscribe anytime.