Guide

Why Didn't My Marchh Activity Create Territory?

Completing a walk or run does not automatically guarantee territory. Marchh may evaluate route geometry, GPS and location quality, activity integrity, territory conflicts and other eligibility conditions before territory is created.

A missing claim does not necessarily mean that the whole activity failed. The activity record and territory result are separate, and Marchh may not expose a single detailed rejection reason for every outcome.

The recorded route may not have closed

Territory needs accepted route geometry that encloses a usable area. A route that ended near its beginning in the physical world may still appear open when GPS drift, missing samples or the final recorded path leaves a gap.

Review the broad route shape without treating the map as survey data. For a future attempt, choose a clear lawful loop and complete it through the normal activity flow rather than editing, replaying or fabricating location information.

Location quality may have been insufficient

Buildings, tunnels, indoor environments, dense tree cover, terrain, device hardware and limited satellite visibility can reduce accuracy. Weak or missing samples may produce gaps, jumps or geometry that cannot define reliable territory.

Check that Location Services, Marchh location permission and Precise Location are enabled where available. Move outdoors to a place with usable signal before starting when practical.

Background recording may have been interrupted

If an intentionally started activity continues while Marchh is backgrounded or the iPhone is locked, required background location permission and operating-system battery behavior can affect sample delivery.

Carry the device throughout the activity and avoid force-closing Marchh. A later restart cannot recreate location samples the device did not provide during the route.

Geometry or territory may conflict

Accepted points can still produce invalid or unusable geometry. Existing authoritative territory can also interact with a new covered area, leading Marchh to reject or modify the result under its current mechanics.

Marchh does not publish a guaranteed size, gap, overlap, timing or priority formula. The live product result is authoritative and the rules can evolve.

Integrity checks may affect the activity

Implausible movement, corrupted information, duplicate activity, GPS spoofing, fake-location tools, automation or manipulated routes may be rejected to protect the shared map.

This guide intentionally does not reveal detection signals or anti-abuse thresholds. Genuine movement and unmodified device data are the appropriate basis for another attempt.

What to try next

Confirm location and Precise Location permission, choose a simple outdoor loop, carry the device for the whole activity, allow required background behavior and finish through the normal flow. Always prefer a safe route over an ideal on-screen shape.

If the same problem repeats in otherwise usable conditions, review Marchh Support and contact support@diplotix.com. Include the app version, iPhone model, iOS version and non-sensitive information that identifies the affected activity.

Questions people ask

Does a closed route always create territory?

No. Closure supplies an area to evaluate, but location quality, route geometry, activity integrity, territory conflicts and other rules still determine eligibility.

Does a visually closed map line guarantee territory?

No. Visual closure is only one part of evaluation; accepted geometry, location quality, integrity, conflicts and other current rules may affect the result.

Can support provide every anti-abuse threshold?

Marchh may withhold integrity-sensitive thresholds and signals so they cannot be used to manipulate activity validation.

Should I repeat the route immediately?

Only when conditions remain safe and appropriate. It can be more useful to check permissions, signal conditions and the recorded shape before another attempt.

Available on iPhone

Move. Close. Claim.

Take Marchh outside and turn qualifying walks or runs into virtual territory on the shared map.