Skip to content
Guides
Newtroubleshooting guide: a rep count that is too low

Fix: a rep count that is too low

Direct answer

Slow the movement and keep the full body area used by the exercise visible in frame. Diagnose one layer at a time and retest after each change, so the result identifies a cause rather than a lucky reset. Use the cited boundary as a test, not as a promise of a universal result.

Launching soon

The App Store link is being confirmed. See how MoveFirst works below.

Symptom
A rep count that is too low
First evidence
10 min · 21 days
Escalation record
Checked 2026-08-15

A practical setup

For a rep count that is too low, capture the iOS version, MoveFirst version, permission state, selected-app count, and whether today is locked or already open before changing settings. Start with the smallest app group or setting that still tests the idea clearly.

Worked example

Run one short reproduction, make one change, lock the iPhone briefly, and repeat the same test instead of toggling several controls together. Run the example with one destination first, then expand only after it behaves as expected.

Use this path only when camera counting works but the displayed total consistently trails a set you completed. Choose a small repeatable set, keep the target fixed, and write down the real repetition count before starting. Move more slowly through the full supported range while keeping the required body area inside the frame; between attempts, change either distance or angle, never both. Compare the size and pattern of the shortfall: missing the first repetition suggests a different clue from losing every second repetition or stopping near the end. Also note whether clothing, shadows, or another moving person entered the image. Manual correction exists but is deliberately narrow — at most two above what the detector saw, and never up from zero — so it will not rescue a badly framed set. If controlled trials remain low, stop compensating with extra exercise, open the day with a step or saved-place option, and send the movement, expected count, observed count, placement, lighting, iOS, and app versions to support.

How to measure the experiment

Use up to 3 reproducible checks across permission, selection, movement input, and today’s open-or-locked state; stop when one layer changes the result. Count planned and automatic openings separately; total minutes alone cannot show whether the pause helped.

Before you switch it on

Good troubleshooting starts with a reproducible case and ends with the smallest confirmed fix.

  • Record the exact expected and observed behavior.
  • Verify the relevant Apple permission first.
  • Retest one selected app or one movement input.
  • Keep versions and results ready if support is needed.

When to adjust the rule

Escalate with the recorded facts when the same test still fails after permission, selection, and a single relaunch are verified. Shorten the access window before raising the physical effort if sessions are simply running too long.

Continue with a related guide

Launching soon

The App Store link is being confirmed. See how MoveFirst works below.

Launching soon

The App Store link is being confirmed. See how MoveFirst works below.

Launching soon

The App Store link is being confirmed. See how MoveFirst works below.