Satellite variables return -1 in feature forms (Internal GPS and External Mock)

Open
#4,721 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, ios
Domain
mobile

Research direction

Start by tracing @position_visible_satellites and @position_used_satellites in iOS feature-form evaluation for the Internal and External (Mock) providers. Compare their handling with the GPS info dialog, then reproduce the form behavior on the listed iPhone environment. Done means unavailable satellite data is saved as empty/NULL rather than -1 and matches the dialog.

Written by the indexing model from the issue text.

Description

bug GPS iOS 🍎

Description
On iOS, @position_visible_satellites and @position_used_satellites return -1 in feature forms with both the Internal and the External (Mock) provider. It also doesn't match the GPS info dialog, which shows N/A.
Project: tester-ws-1/test_external_receiver

Environment

  • Device: iPhone 15
  • OS: iOS 26
  • App build: 2026.5.0 (952111)
  • Affected providers: Internal, External (Mock)

Steps to reproduce

  1. Set the position provider to Internal.
  2. Open a feature form whose fields use @position_visible_satellites and @position_used_satellites.
  3. Add a feature and check the values.
  4. Switch the provider to External (Mock) and repeat steps 2–3.

Actual results
With both providers, @position_visible_satellites and @position_used_satellites return -1, and -1 gets saved to the feature as if it were real data.

Image

Expected results
The variables return real values. If there's no satellite data, they return empty/NULL, matching what the GPS info dialog shows.

Screenshots

Image
Dominant language
C++
Stars
394
Forks
91
Avg merge
2d 10h
Merged PRs (30d)
16

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/mobile

All issues in MerginMaps/mobile

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.