Skip to content

FreqMapper v1.0.10

Summary

FreqMapper v1.0.10 adds Watchers to both mobile maps, supports Meshtastic radios over TCP, and lets wardrives start and keep recording when the FreqMapper server or map tiles are unavailable. It also makes repeated iOS TestFlight testing notes clearer.

What's new

  • Positioned Watchers now appear on the Android and iPhone maps using their Meshtastic short names.
  • Android and iPhone can save and connect to Meshtastic radios over TCP using a hostname or IP address and port.
  • Active Patrol and Silent Recon can start without a reachable FreqMapper server when the required saved region and offline approval are available.

Improvements

  • When remote map tiles are unavailable, mobile wardrives keep the phone marker and a breadcrumb visible on a blank driving canvas.
  • Encrypted wardrive evidence remains queued locally and resumes uploading after any connection capable of reaching the FreqMapper server returns.
  • Android's release workflow now has a manually selected internal self-test destination, separate from closed testing and production.
  • When an iOS TestFlight build has the same app code as the previous build, its notes explicitly explain that no app-code changes were detected.
  • Testing guidance is carried forward as “Areas to retest” rather than presented as new changes, so testers can see which checks remain relevant.
  • Across repeated builds with unchanged app code, the notes reference the immediately preceding build without accumulating older explanations.

Fixes

  • Fixed offline wardrive startup depending on a currently reachable server or successfully loaded remote map.
  • Fixed Silent Recon being able to reach an unusable offline start path that could close the app instead of beginning local collection.
  • Fixed reused TestFlight notes showing an earlier build’s “What to Test” heading. The heading and “Focus for build” section now identify the build being tested.
  • Copied notes with an outdated build heading can be corrected while preserving hand-edited notes.

What you need to do

App users do not need to take any action until a mobile test build is made available. After this change is merged, release operators can manually publish Android 0.1.109 (110) to the Google Play internal-testing track and should run Watch TestFlight releases once to repair build 881's copied notes.

Mobile availability

Android 0.1.109 (110) is prepared as an internal-testing candidate but has not been uploaded. The iPhone changes have not yet been evidenced in a processed TestFlight build. No public mobile release is included in this change.

Known limitations

The automatic repair is intentionally limited to an exact copied automated note whose heading names the earlier same-source build. Hand-edited notes remain unchanged. TCP radio behavior, offline collection, background recovery, and the updated maps still require physical Android and iPhone testing with real radios.