Skip to content
iOS SDK

iOS, reported with the whole story.

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

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.

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.

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: "0.9.0")

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.