MerginMaps / MerginMaps/mobile

Position variables not available/populated (@position_vertical_speed, @position_magnetic_variation); on iOS satellites info missing and “-1” values

Open
#4,090 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug GPS
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

Description

  • In feature forms, the position variables @position_vertical_speed and @position_magnetic_variation are not available/populated for both internal and external GPS on Android and iOS.

  • On iOS, the GPS info dialog shows N/A for “Visible satellites” and “Used satellites” for Internal

  • On iOS, the GPS info dialog shows ❓ for “Visible satellites” and “Used satellites” External (Mock) @IvaKuklica please verify

  • On iOS, internal GPS, In feature forms, satellite variables return -1 (e.g., @position_visible_satellites, @position_used_satellites) ❌

  • On iOS, External (Mock), In feature forms, satellite variables return -1 (e.g., @position_visible_satellites, @position_used_satellites) ❓ @IvaKuklica please verify

  • iOS: if External (Mock) provider is set, Horizontal accuracy and Vertical accuracy shows constant values:
    -> Horizontal accuracy: 5.00 m (constant)
    -> Vertical accuracy: 9.50 m (constant) ❓ @IvaKuklica please verify

  • Network position provider - iOS: Satellites in use and in view are the same, e.g. 7/7, the same in form ❌

  • Android, network pos. provider, external GPS: @position_used_satellites is higher (+1) than @position_visible_satellites (inconsistent). ❌

  • Projects used: tester-ws-1/test_orthometric_heights or test_external_receiver

Related (for context): #1743 (vertical speed), #1753 (external GNSS satellite info). Those do not cover magnetic variation nor the iOS -1 counts with internal GNSS.

Environment
PROD

Application (+ app version, build, operating system)

  • Actual Android app version: 2025.6.0
  • Samsung Galaxy A53 5G, Android 15
  • Actual iOS app version: 2025.5.0
  • iOS 18.5, iPhone

Steps to reproduce

  1. Open project tester-ws-1/test_external_receiver.
  2. Ensure GPS has a fix.
  3. Internal GPS: add new feature in GPS_data layer; in the form, observe fields:
    • @position_vertical_speed
    • @position_magnetic_variation
    • @position_visible_satellites
    • @position_used_satellites
  4. External GPS: connect an external GNSS receiver, set it as the position provider, and repeat step 3.
  5. On iOS, open the GPS info dialog and verify “Visible satellites”, “Used satellites”, “Horizontal accuracy” and “Vertical accuracy”.
  6. Repeat for network position provider.

Actual results

  • @position_vertical_speed and @position_magnetic_variation are empty (internal and external GPS; Android and iOS). ✅
  • iOS GPS info dialog: “Satellites (in use/view)” display N/A
  • iOS GPS info dialog: “Horizontal accuracy” and “Vertical accuracy” display constant values (5.00 m/ 9.50 m). ❓
  • iOS feature form: @position_visible_satellites and @position_used_satellites evaluate to -1.
  • iOS: If the network position provider is configured, the number of used satellites is the same as satellites in view.
  • Android, network pos. provider, external GPS: @position_used_satellites is higher (+1) than @position_visible_satellites (inconsistent).

Expected results

  • @position_vertical_speed and @position_magnetic_variation are available and populated when measurable (null only when not available).
  • iOS GPS info dialog shows “Visible satellites” and “Used satellites”.
  • iOS GPS info dialog shows “Horizontal accuracy” and “Vertical accuracy” or N/A ❓
  • Satellite variables return 0 or positive counts (not -1) when a fix is available.

Screenshots or logs

Conclusion
Created by GitHub Copilot and supervised by a human test analyst.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the GPS data form and GPS info dialog checks in tester-ws-1/test_external_receiver, then compare internal, external, and network providers on Android and iOS. Inspect how @position_vertical_speed, @position_magnetic_variation, @position_visible_satellites, and @position_used_satellites are populated. Done means measurable values are exposed consistently, unavailable values are null or N/A, and satellite counts are nonnegative and consistent across the listed providers.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.