Reference
30Troubleshooting
Symptoms, likely causes and fixes for the problems pilots hit most often.
Mixed, see chapter
Recording and GPS#
| Symptom | Likely cause | Fix |
|---|---|---|
| The start button will not enable | No layout or no glider selected | Choose both on the Flight tab. The app says Select a layout and glider to enable the button. |
| Location permission is required to record your flight | Location was declined or is restricted | Grant location for SkyTrackPro in the device settings, then reopen the app. See Install and first run. |
| The screen stays on Waiting for takeoff | The app has not detected a launch yet | Normal on the ground. If it persists in flight, check the GPS status chip for a poor fix. |
| Altitude looks wrong | The barometer setting does not match your hardware, or QNH is off | Check Use device pressure sensor and Use device baro in Vario and sound, and the QNH in Airspaces. |
| The flight ended by itself | Automatic landing detection | Press Still flying next time when the countdown appears. See Recording a flight. |
The map#
| Symptom | Likely cause | Fix |
|---|---|---|
| The map is blank but the track and task still draw | No connection and no offline region for this area | Download a region for the area. See Offline maps. |
| The map is blank on mobile data but fine on Wi-Fi | Use mobile data for maps is off | Turn it on in Maps, or download a region. |
| Map not ready yet | The map is still initializing | Give it a few seconds. If it persists, leave and reopen the flight screen. |
| The map keeps moving on its own | Auto zoom is doing its job | Narrow the auto zoom range or turn auto zoom off in Maps. |
| The map moves when I do not mean it to | Touch gestures | Turn off Touch gestures in the flight menu and use zoom and pan tiles or a remote instead. |
| The side view shows No terrain data | No terrain heights for this area | Download an offline region, or open the area once with a connection. |
Bluetooth hardware#
| Symptom | Likely cause | Fix |
|---|---|---|
| Scanning finds no vario or glasses | Bluetooth off, permission missing, or the device is not on | Read the exact message. The app distinguishes Bluetooth off, permissions denied, location services disabled and unsupported hardware. |
| Bluetooth / location permissions are not granted. | Permissions declined earlier | Enable them for SkyTrackPro in the system settings, then reopen the picker. |
| The vario connects but the data looks wrong | The wrong sensor is being preferred | Review Use device GPS and Use device baro in Vario and sound. |
| I cannot tell whether the vario is connected | The status chip is not on the layout | Watch the External vario chip, or open the Bluetooth vario logger to see raw data arriving. |
| The remote does nothing | The input mode is Off, or nothing is assigned | Set Remote input mode and assign actions. See Remote controls. |
| The glasses image is off center | Screen position not calibrated for your face | Send the calibration pattern and adjust Screen position. See ActiveLook glasses. |
Live tracking, uploads and the server#
| Symptom | Likely cause | Fix |
|---|---|---|
| Followers see a gap in my live track | No coverage for that stretch | Normal. The gap fills when the signal returns, unless the app was force closed. See Internet connection. |
| Level messages or emergency buttons are unavailable | No task loaded, no live tracking, or the flight is not recording | The app names the missing condition, for example Load a task to send level messages. |
| Upload failed | No connection, or the flight has too few points | Retry with a signal. A flight needs at least two track points. |
| This flight is already uploaded. | It was uploaded before | If you deleted it on the website, use Reset upload state and upload again. |
| The XContest submission failed | Account not connected, or a transient error | Connect the account in the logbook actions menu. The flight is still on SkyTrackPro and can be submitted from the website later. |
| A competition task is not visible | Your registration status does not grant access yet | The app explains it as No tasks are available for your current registration status yet. Ask the organizer. |
| The share card map will not load | That map needs a connection | Build the card with a signal, or choose a style that is not map based. |
Tasks#
| Symptom | Likely cause | Fix |
|---|---|---|
| Could not parse a task from the QR code or file. | The code was damaged, too small, or the file is not a task | Ask for the .xctsk file instead of rescanning. |
| I cannot create a task | No waypoint list imported | Import a .wpt, .cup or .gpx file in Tasks, then Waypoints. |
| DEM validation incomplete | Ground heights for some turnpoints could not be resolved | Open the task once with a connection, or download an offline region covering the task area. |
| Arrival height at goal looks wrong | Unresolved goal elevation, or an elevated goal | Check the task warnings and the goal settings. See Tasks. |
| The start countdown is wrong | The start time or gates are set incorrectly | Check Basic info in the task editor against the briefing. |
Battery and screen#
| Symptom | Likely cause | Fix |
|---|---|---|
| The battery does not last the flight | Screen on, live tracking, buddies and streamed map tiles together | Turn on Battery save mode, use a downloaded region, use the dark theme, and turn the buddies overlay off when you are not using it. |
| The screen dims while I am reading it | Battery save mode idle timeout | Lengthen Dim after, or turn battery save mode off. |
| The screen goes to sleep in flight | Keep screen on during flight is off | Turn it on in Settings, then Other. |
Getting help#
If this chapter did not answer it, ask in the forum. It is the right place for anything that starts with a question rather than a crash: how to set something up, which setting does what, why the app behaves the way it does, or how other pilots have solved the same thing.
Questions and how do I
skytrackpro.app/forum, where other pilots and the developers answer.
Feature ideas
The same place. Ideas that come with a reason tend to get built.
Bugs
Also the forum, with a diagnostic bundle attached. See below.
Tip
Search the forum before posting. Most questions about a flying app have been asked by someone flying the same site, and the answer is usually more useful than a manual page because it comes with local context.
A good forum post answers four things: what you were trying to do, what you expected, what happened instead, and your app version. You can copy the version by tapping App version in Settings, then Other.
Note
A link to the forum sits in the footer of every page of this manual, so you never have to come back here to find it.
Reporting a bug#
When something is genuinely broken rather than confusing, a diagnostic bundle is worth more than any description.
- Turn on Debug mode in Settings, then Other. Add Verbose logging if the problem is hard to reproduce.
- Reproduce the problem.
- Press Send debug log to support and share the bundle out of the app, then attach it to your forum post.
- Include your app version and a short description of what you expected.
- Turn verbose logging off again.
Tip
The single most useful thing you can include is what you were doing in the thirty seconds before it went wrong. Logs show what happened, not what you intended.
Note
If you are not sure whether it is a bug or a misunderstanding, ask in the forum first. It costs you nothing and it is often answered the same day.