Skip to content

In-app bug reporting: shake to report, with the network and logs attached

Updated

Midge's SDKs put a Report a bug flow inside your own app. Someone using it shakes the phone, or taps your button, records the screen and says what went wrong. The report reaches your Midge workspace with what the app did in that time: its HTTP requests and responses, its log messages, the device, and the context you set, such as the user's ID or plan.

It's the difference between a support ticket that says "checkout is broken on my phone" and one that shows the tap on Pay, the 502 from /api/orders and the user's plan, on one timeline.

Three platforms, one workspace

PlatformHow you add itNetwork capture
Websites and web appsOne <script> tagfetch and XMLHttpRequest
iPhone and iPad (iOS 17+)Swift packageURLSession
Android (API 26+)Kotlin libraryOkHttp, HttpURLConnection, Volley, or Midge.network()

Every SDK sends to a recording link, so reports land in the same workspace as the ones your team makes with the Chrome extension, the Mac app and the iPhone and Android apps.

Set it up on iOS

import MidgeSDK

@main
struct ShopApp: App {
    init() {
        Midge.start(link: "rl_YOUR_TOKEN")
    }
}

Shaking the phone now opens the report sheet. To open it from your own button, call Midge.report(). Full setup: iOS SDK docs.

Set it up on Android

class ShopApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        Midge.start(this, link = "rl_YOUR_TOKEN")
    }
}

val client = OkHttpClient.Builder()
    .addInterceptor(Midge.okHttpInterceptor())
    .build()

Code that uses HttpURLConnection or Volley calls Midge.openConnection(url) instead of url.openConnection(). Full setup: Android SDK docs.

Set it up on the web

<script src="https://midge.dev/sdk/v1.js" data-link="YOUR_LINK_TOKEN" async></script>

A Report a bug button appears in the corner of your site. Full setup: website SDK docs.

What each report contains

  • The screen recording, of your app only: other apps and notifications are not recorded.
  • Network requests with headers, bodies up to 64 KB, status and timing.
  • Logs: on iOS your app's Logger, os_log and NSLog messages; on Android your app's own logcat lines; on the web the console. Midge.log() adds lines of your own.
  • Device: app name, version and build, device model, OS version, language and time zone.
  • Metadata you set with Midge.metadata(), and the reporter's name and email from Midge.user().

Requests from the last few minutes are kept in memory only, and nothing is sent unless the person taps Send.

Redacted on the device

Before anything leaves the phone or the browser, Midge removes passwords, tokens, cookies, authorization headers and card numbers, masks emails and phone numbers, and applies your workspace's own hidden field names. On mobile, this runs the same redaction code as the Chrome extension, so a token is caught the same way everywhere. See redaction.

Only your app can send

On the web, the SDK sends only from domains your workspace has verified. On mobile, an owner or admin registers the app's bundle id or application id in the workspace; for any other app, the report sheet says so and sends nothing.

Why not build it yourself

A "Send feedback" form that emails a text box is easy. What's hard is everything a developer needs next: a recording of what the person did, the request that failed and its response body, the log lines around it, and confidence that none of it contains a customer's password or card number. Building, redacting and storing that for three platforms is a project of its own. With Midge it's a few lines per app, and the reports arrive where your team already works.

From report to fix

Each report opens on midge.dev with the video and the logs side by side, an AI summary with steps to reproduce, and one-click hand-off to Jira, Linear, GitHub or Slack through integrations. Coding agents such as Claude Code and Cursor read the same report through Midge's MCP server.

Midge is free: unlimited recordings, videos up to 15 minutes, and no watermark.

Frequently asked questions

Which platforms do the SDKs support?
Websites and web apps through a script tag, iPhone and iPad apps (iOS 17 or later) through a Swift package, and Android apps (Android 8.0, API 26, or later) through a Kotlin library.
How does a user open the report sheet?
In mobile apps, by shaking the phone or from your own Report a bug button that calls Midge.report(). On the web, from a Report a bug button the script adds, or one of your own.
Which network requests are captured?
On iOS, URLSession requests. On Android, OkHttp (and Retrofit, Coil and Ktor's OkHttp engine) through an interceptor, HttpURLConnection and Volley, and any other client through Midge.network(). On the web, fetch and XMLHttpRequest.
Is sensitive data sent to Midge?
No. Passwords, tokens, cookies, card numbers and your workspace's own hidden fields are redacted on the device, by the same code as the Chrome extension, before anything is sent.
Are the mobile SDKs available now?
The website SDK is available to every workspace. The iOS and Android SDKs are in early access: email [email protected] with your app's name to get access.