SummitPulse

Known limitations

Things SummitPulse does on purpose that can look like faults. If something here explains what you saw, it is behaving correctly — which is not the same as it being what you wanted, so each one says what to do about it.

The watch app is a companion, not a standalone app

SummitPulse for Apple Watch is tied to the phone app: it is installed through the Watch app on your iPhone rather than from the watch, it cannot be added to a watch whose paired iPhone does not have SummitPulse, and removing the phone app removes it from the watch too.

What to do: Install the phone app first. If the watch app is missing after a reinstall, add it again from Watch on the iPhone — see Support.

The watch needs the phone with you

The watch does not record GPS of its own — the phone does, and sends the route and distance across. That is a deliberate battery decision, and it means a hike recorded with the phone left in the car has heart rate and elapsed time but no route.

What to do: Carry the phone. A pocket or pack is fine; it does not need to be in your hand or awake.

If the two lose contact, the route has a gap

The watch keeps recording heart rate and remembers what happened while it was out of range, then hands it over when they reconnect, so you get one hike rather than two. But nothing recorded the route during that stretch, so the line on the map has a gap in it.

What to do: Nothing to do, and nothing is lost that was ever captured. Distance across the gap is estimated from the points either side.

Each number has exactly one source

Heart rate and calories come from the watch. Distance, elevation, pace and moving time come from the phone. Neither device recomputes the other's numbers, so they cannot drift apart — but it also means a figure is missing rather than approximated when its source was absent.

What to do: A blank is a blank on purpose. The app never shows a zero it had to invent.

Recording stops when the screen locks, unless background location is on

This is the single most common cause of a short hike. Location granted only while the app is open is exactly what the phone does with it — the moment the screen locks, it stops.

What to do: Grant “Always” on iOS or “Allow all the time” on Android. The app links straight to the right page.

A driving prompt left unanswered keeps the hike paused

If it thinks you have started driving it pauses and asks. It will never finish a hike on its own — that is a deliberate limit, because a wrongly finished hike cannot be undone the way a wrongly paused one can. The cost is that an unanswered prompt leaves the hike paused until you notice.

What to do: Answer it, or resume when you next look. A resumed hike keeps everything recorded before the pause.

The map may be blank without a signal; the hike is not

Map tiles come from the network. On a ridge with no signal the background can be empty or stale, which looks alarming mid-hike.

What to do: Your route still draws on top of it, and distance, elevation and time are unaffected. Recording never needs a connection.

Altitude at a point is approximate, not surveyed

Altitude comes from GPS. Elevation gain — how much you climbed — is the number the app is built around and the one it works to keep honest. The absolute altitude shown at a point is a rougher figure and will not match a trail sign or a surveyed summit marker.

What to do: Trust the gain. Treat a single altitude reading as approximate.

There is no cloud copy

No account and no upload means no server-side backup. Hikes live on the device. If the phone is lost or wiped, hikes that were never exported are gone with it.

What to do: Archive your history to a file periodically, and keep it wherever you keep other backups. See Support for how.

Something not on this list?

If the app did something this page does not explain, that is worth reporting rather than working around. See Support, and check Compatibility for which devices are tested before release.