Guides
Crash reporting
Find which builds are crashing and where to start debugging. With telemetry consent and crash reporting enabled, the iOS SDK saves fatal crash reports for upload on relaunch. Upload matching debug symbols for readable stacks.
What Pharen captures
Crash reporting captures fatal crashes and the handled errors your app reports.
- Fatal crashes — uncaught Objective-C / Swift exceptions and the fatal POSIX signals (
SIGSEGV,SIGBUS,SIGILL,SIGFPE,SIGABRT,SIGTRAP). Each report carries the crash-site call stack, the loaded binary images (with their debug ids, for symbolication), and the identity of the build that died — its version and build number, read at crash time, not upload time. - Handled errors — anything you report yourself with
recordError(…), delivered through the normal event queue.
Pharen's handlers chain: any exception handler already installed still runs, and signals are re-raised to the default handler, so the operating system's own crash report is still produced. Pharen adds a report; it doesn't replace the platform's.
Reporting handled errors
For non-fatal failures — a caught exception, a degraded code path — record an error with as much or as little context as you have. Breadcrumbs are free-form strings that describe what led up to it:
Pharen.shared?.crashReporting.recordError(
"Checkout failed: payment gateway timeout",
stack: Thread.callStackSymbols,
severity: .error,
breadcrumbs: ["tapped_pay", "network_slow"]
)Handled errors are a telemetry-class event, so they follow the same consent gate and the same durable queue as everything else.
Delivery after relaunch
Pharen saves a fatal crash report to disk and attempts to upload it the next time the app launches. A network failure leaves the report available for a later attempt, within the SDK's storage limits. Each retry keeps the original report ID so the server can deduplicate it.
Ready to move beyond evaluation? Organization approval unlocks test and live keys and uploads of matching dSYMs for readable crash stacks. Your paid plan determines which features and usage limits apply. Go to organization approval.
Upload dSYMs for readable stacks
A crash from a release build arrives as memory addresses. To turn those into function names and line-adjacent frames, Pharen needs the build's dSYMs (debug symbol bundles). Crashes and symbols join on the binary's embedded debug id — never on a version string or a file path — so uploading is order-independent: symbols can arrive before or after the crash.
Upload symbols once per build, whichever way you ship:
- fastlane plugin —
pharen_releaseuploads every dSYM the archive produced, automatically. - Xcode run script — a build phase that uploads dSYMs on archive, no fastlane required.
- The release lane or the CLI directly (
pharen symbols upload).
Grouping into issues
Raw crash events are collapsed into issues so a hundred reports of the same bug are one line, not a hundred. Grouping fingerprints the symbolicated stack — primarily the exception type and the top frames in your code — and deliberately ignores the volatile parts (memory addresses, line numbers, hashed paths) that change build to build. Stackless errors are grouped by a parameterized form of their message (numbers, ids, and quoted values normalized to placeholders).
Issues carry the builds they were seen on. When a crash that had been resolved turns up again on a build it was never seen on, the issue reopens as a regression carrying the build it came back on, instead of the crash being silently re-counted. Pharen decides that from the build the crash happened on — never from assuming a higher build number is a later build. A build number can tell Pharen which build a crash landed on, never whether that build carries your fix.