When something goes wrong in iFly, a bug report sends us the app's own log so we can see what it was doing. For problems with an ADS-B receiver (traffic, weather, position from the receiver, or the attitude on the EFIS) we also need a recording of the receiver's data stream, which you switch on separately. Both take about a minute.
Send a bug report
Works the same on Android and iOS. If iFly crashed, just open it again and send the report: the log from the previous run is attached automatically. If the problem is happening right now, send the report while it is happening, without closing iFly, so the current log is included.
- Tap Menu › About › Send Bug Report.
- iFly asks Bug Report - Select Log File. Tap Use Default to attach the log from the previous run of iFly (on iOS, the two previous runs). Tap Select Log instead if the problem was on an earlier day; the list shows each run by date and time.
- Your email app opens with the report addressed to us and the log attached. iOS uses the built-in Mail app, so an email account must be set up in Mail.
- Above the log text, type what happened and what you were doing when it happened, then send.
One sentence saves a day
A report with no description is the most common reason we have to write back before we can start. Two lines are plenty: what you saw, and what you tapped just before.
The report contains the app log: iFly version, tablet model, settings, GPS fixes, ADS-B message counts and your current flight plan. If you already have a ticket open with us, mention it in the description and we will attach the report to it.
When we need an ADS-B log
The app log records that a receiver connected and counts its messages, but it does not keep the messages themselves. For the problems below the developers need the raw data stream, so support will usually ask you to send an ADS-B log as well:
- The EFIS or synthetic vision shows a bank or pitch that does not match the airplane, or draws upside down.
- Your position from the receiver jumps, freezes or sits at zero speed.
- Traffic targets are missing, duplicated or at the wrong altitude.
- The receiver connects but weather never fills in, or iFly cannot tell which receiver it is.
Record and send an ADS-B log
- Tap Menu › Setup › ADS-B › Options › Enable ADS-B Logger. A check mark appears next to it, and iFly shows ADSB Recording has Started as soon as data arrives from the receiver.
- Each time iFly starts it asks Keep ADS-B Logging Enabled? Tap Yes until you have caught the problem. Answering No switches the logger off.
- With the receiver connected, reproduce the problem. A few minutes is enough. For attitude problems, sitting level on the ramp with the EFIS open is fine; it does not have to be in flight.
- Fully close iFly with Menu › Exit Application › Shutdown Application, then open it again. This finishes the recording.
- Tap Menu › About › Send Bug Report, then Select Log. Scroll to the bottom of the list. Recordings are named Adsb_ followed by the date and time they started, for example Adsb_2026_09_20-08.23 (5.2 MB). Pick the one from the run with the problem and tap Select.
- Your email app opens with the recording attached. Add a sentence about what you saw and which receiver you have, then send.
- When you are done, turn the logger off: tap Enable ADS-B Logger again to clear the check mark, or answer No the next time iFly asks.
Send it soon
iFly keeps only the most recent few recordings and deletes older ones as new flights are recorded. A long flight can produce a file of tens of megabytes; if your email app refuses to send it, tell us and we will arrange another way to get it.
The recording holds the receiver's data stream exactly as iFly received it: heartbeat, ownship position, traffic, weather and attitude messages. Nothing from your account or other apps is included. Opening the log list while a recording is running stops that recording, which is fine.
Related