Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[iOS] GPS info dialog shows N/A for visible and used satellites (Internal GPS and External Mock)

Open
#4,725 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
56/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, ios
Domain
mobile

Research direction

Start at the iOS GPS info dialog and trace how satellite values are obtained for the Internal and External (Mock) providers. Reproduce the issue with both providers, then verify that supplied satellite data is displayed and that unavailable data receives a clear message.

Written by the indexing model from the issue text.

Description

bug GPS iOS 🍎

Description
On iOS, the GPS info dialog shows N/A for "Visible satellites" and "Used satellites" with both the Internal and the External (Mock) provider. Users can't see any satellite information, even when the provider may be sending it.

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 the GPS info dialog after getting a position fix.
  3. Check "Visible satellites" and "Used satellites".
  4. Switch the provider to External (Mock) and repeat steps 2–3.

Actual result:
With both providers, both fields show N/A.

Image

Expected result:
"Visible satellites" and "Used satellites" show real values when the provider sends them. If the platform or provider doesn't provide satellite data, the dialog should say clearly that the data isn't available.

Attachments:
Image

Image
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 9h
Merged PRs (30d)
15

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.