Skip to content

Releases: spatie/flare-client-swift

1.0.0

Choose a tag to compare

@freekmurze freekmurze released this 08 Sep 09:50
06b7e20

Stable Swift 6 client for reporting errors and native crashes to Flare.

  • Report caught errors with context, breadcrumbs, filtering and supplied stack frames.
  • Capture native crashes with PLCrashReporter and upload them on the next launch. Failed uploads remain in a bounded local queue.
  • Include device model, OS, architecture and timestamped memory diagnostics. Flare's Application context displays readable values such as 48.00 GB and 3.52 MB.
  • Return delivery failures without throwing into application error paths.

Supports macOS 12+, iOS 15+ and tvOS 15+. The core reporting client also supports Linux. Uses JavaScript compatibility metadata for Flare ingestion; native source-level symbolication is not included.

Verified with 36 SDK tests, macOS and Linux CI, and native crash recovery from an isolated Bloom process.

Full Changelog: 0.1.1...1.0.0

0.1.1

Choose a tag to compare

@freekmurze freekmurze released this 08 Sep 09:36
94174d2

Add device model, total RAM and timestamped available-memory estimates to reports. Native crash capture refreshes diagnostics every 30 seconds and preserves the last sample across a restart.

Available memory is a free-plus-inactive system memory estimate on Apple platforms. Missing samples are never replaced with post-restart memory readings. Includes tests for snapshot preservation, refresh failure and overflow handling.

0.1.0

Choose a tag to compare

@freekmurze freekmurze released this 08 Sep 08:45
90fa743

Initial Swift Package Manager release with error reporting, structured context, breadcrumbs, and optional native crash capture through PLCrashReporter.

Crash reports are saved locally and uploaded on the next launch. Upload failures return safely and remain queued for a later attempt. Includes macOS and Linux tests and a standalone macOS example.

Flare currently uses JavaScript compatibility metadata for ingestion. Native frames contain binary names and offsets; source-level symbolication is not included.