FlightLedger — Support

This document covers how to get help, common issues, and troubleshooting for FlightLedger (iOS 17+).

Getting help

Requirements

Troubleshooting

Build & run

"Please select an available device or choose a simulated device as the destination."

In Xcode, use the destination dropdown in the toolbar and choose an iPhone simulator (e.g. iPhone 16).

"No profiles for 'com.flightledger.app' were found"

You're building for a physical device but no provisioning profile exists. In Xcode, select the FlightLedger target → Signing & Capabilities → enable Automatically manage signing and choose your Team.

App behavior

"Airports CSV not found"

The app looks for airports.csv (OurAirports format) inside Resources/Airports/. Ensure Resources is included in the target's Copy Bundle Resources.

Barcode scan doesn't recognize my boarding pass

FlightLedger uses BCBP (Bar Coded Boarding Pass). Ensure the barcode is in frame, well lit, and the full code is visible. Try manual entry or OCR (photo) as a fallback.

OCR (photo) import is wrong or missing fields

Results depend on image quality, angle, and font. Use a clear, flat photo of the boarding pass or itinerary. You can correct the extracted fields in the confirmation step before saving.

FAQ

What is FlightLedger?

An iOS app to record flights (via barcode scan, OCR, or manual entry) and view them in a list and on a world map.

Where is my data stored?

On the device only, using SwiftData (local persistence). No data is sent to a server by the default app.

Minimum iOS version?

iOS 17.0 or later.

Reporting bugs

When reporting a problem, please include:

  1. What you did (e.g. "Scanned a boarding pass")
  2. What you expected
  3. What actually happened
  4. Environment: Xcode version, iOS version (device or simulator)
  5. Exact error message (if any)

Last updated for FlightLedger skeleton (iOS 17+, SwiftUI, SwiftData).