Skip to content
Everframe
Sign inGet started →
iOS SDK

iOS, reported with the whole story.

Reports with the whole story from your iOS and iPadOS apps.

Get started → See a real report

Everframe captures a native screenshot, console and network state and the trail of screens that led to the bug — forwarded to your webhook or our dashboard, ready to act on.

screenshot + annotationsreplay (per app)logsnetwork (opt-in)screen trailcrash reportsdevice

In-app bug reporting for iOS and iPadOS

Shipping a polished iPhone or iPad app means catching the bugs your users actually hit — the layout that breaks on one device size, the button that does nothing, the request that quietly fails. Everframe embeds a bug reporter directly in your iOS app, so testers, QA, and real users can report a problem in a single tap without leaving the screen they’re on.

How capture works on iOS

When the reporter opens, the iOS SDK takes a native screenshot of exactly what’s on screen — no screen-recording prompt, no camera — and pulls the recent console logs, network calls and the trail of screens the user moved through. Sensitive views can be marked so they’re masked before anything leaves the device. It’s all packed into one envelope and forwarded to your tools or the dashboard.

Quick capture for your team

Your team doesn’t need the reporter. Link a test iPhone or iPad to yourself once under Project settings → Devices: open Link a device, shake the phone and click the number it shows. From then on a shake files a private draft with the screenshot, replay and logs, and the phone shows “Captured · your name”. You title it on the dashboard. A shared QA device can be linked to the team instead, so its captures land in the inbox. On your users’ devices shake keeps doing what it does today. See Quick capture on real devices.

Ready to act on

Because each report carries the surrounding console and network state and the trail of screens that led there — not just a flat screenshot — a developer or an AI coding agent can act on the bug instead of asking what happened.

Crash reporting on iOS

Swift traps, uncaught Objective-C exceptions and fatal signals become reports on the next launch. Foreground memory and watchdog kills are reported as inferred terminations, without a stack. Errors your app passes to captureException are reported too, with the app version and the device.

What every iOS report carries

  • The trail of screens and actions leading up to the report — navigation, taps and errors.
  • A screenshot with the reporter's annotation, masked for PII.
  • Console logs and network calls from the seconds before the report.
  • App, SDK, OS and device metadata.

Install

// Package.swift
.package(url: "https://github.com/scriptx-com/everframe", from: "1.2.1")

Questions

Does Everframe support iPad?

Yes. The iOS SDK covers iPhone and iPad (iPadOS); the report captures the same envelope on both.

What is in an iOS report?

A structured, typed envelope — screenshot, console, network and the action trail that led to the bug — so whoever picks it up starts from evidence, not a guess.

How does my team report bugs without the form?

With quick capture. Link a test iPhone or iPad to yourself under Project settings → Devices in the dashboard, then shake it. A private draft with the screenshot, replay and logs lands in the dashboard's capture card, and you title it there. Your users' release builds don't change.