MerginMaps / MerginMaps/mobile

Using an FLX 100 GPS (Leica) on a Windows tablet make mergin maps crash

Open
#2,949 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug data corruption - sync failure - crash - anr desktop GPS Windows 🪟
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

Hi,

I've tried to connect an FLX 100 GPS as an external GPS receiver on mergin maps installed on a windows tablet. Mergin maps recognize the GPS receiver, but when I select the GPS mergin maps keeps going from connected to disconnect and after a few attempts, mergin maps crash. Here are the last lines from the terminal :

"2023-12-07T10:01:13.290Z Internal GPS provider: Unable to create default GPS satellite source\n"
"2023-12-07T10:01:13.320Z BluetoothPositionProvider: Socket changed state, code: ClosingState\n"
"2023-12-07T10:01:13.337Z BluetoothPositionProvider: Socket changed state, code: UnconnectedState\n"
"2023-12-07T10:01:13.337Z PositionKit: Changed position provider to: devicegps\n"
"2023-12-07T10:01:20.422Z Internal GPS provider: Error occured (position source), code: 2\n"
"2023-12-07T10:01:49.577Z Input: \"Application changed state to:\" Qt::ApplicationInactive \n"
"2023-12-07T10:01:57.197Z Input: \"Application changed state to:\" Qt::ApplicationActive \n"
"2023-12-07T10:02:01.136Z Input: \"Application changed state to:\" Qt::ApplicationInactive \n"

Do you know what could I do in order to avoid mergin maps to crash ?

Thanks.

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

Reproduce the connection on a Windows tablet with the Leica FLX 100 GPS and capture the terminal output shown in the report. Start by investigating the GPS provider and Bluetooth connection transitions; done means the receiver stays connected without repeated disconnects or a Mergin Maps crash.

Written by the indexing model from the issue text.

Assessment

Domain
mobile-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.