What’s new in BugScreen

The console now adapts to the screen it's on. On a narrow screen the sidebar becomes a menu button in the top bar, and tapping it opens the same navigation you get on a desktop — the app switcher with its search, Apps, Billing, Documentation, Quick jump, and your account menu. Pages, dialogs and long values like API keys reflow to fit the width instead of running off the edge.

So a console link you open on your phone — a teammate's invite, a billing prompt, a quick check on an app's integrations — is something you can act on there and then, rather than something that waits until you're back at a laptop. There's nothing to switch on, and the desktop layout is unchanged.

Every app in your console now has a BugScreen app tab with a join link, a QR code and a short code you can send to testers. They install the BugScreen app from Google Play, pair with the invite, and start filing reports against that app straight away — no SDK, no code change, no new build.

That covers builds you can't instrument at all — a partner's app, a vendor build you're evaluating — and lets a QA lead get a first ticket flowing without waiting on a mobile developer. Reports land in the same GitHub, Jira, ClickUp and Slack integrations as SDK reports, and count against the same monthly allowance. Invites are admin-issued and can be rotated at any time, optionally disconnecting every device paired to that app — not only the ones that used the invite you're replacing — so a leaked invite can be fully undone.

Testers can now annotate a captured screenshot right in the bug-report screen. Open a screenshot from the full-screen preview, tap Markup, and draw a box, arrow, or freehand stroke in your choice of colour to point the developer straight at the problem.

The Redact tool blurs or blacks out anything sensitive — emails, names, tokens — and the redaction is baked permanently into the image on the device, so private data never leaves the phone. Available on both the iOS and Android SDKs with no configuration needed.

Your SDKs can now tell BugScreen which account a report was filed under. Call setUser with an account id and role (email optional) — for example on login — and every report from that session carries it. On Android and iOS you can instead hand us a small closure with setUserProvider, and we read the current account at the moment the report is captured, so a tester switching between logins always gets the right one attached.

The account then leads the created issue: a dedicated Account section at the top of your GitHub, Jira, or ClickUp ticket, with the role as a filterable label so you can slice reports by admin, pro, free, or whatever roles your app uses. By default only the non-identifying fields are surfaced — email is opt-in, and nothing is collected automatically.

You can now pay for Pro and Team annually instead of monthly. Flip the new Monthly / Annual toggle on the pricing page: annual plans are billed once a year at a discount, shown as the per-month equivalent with the savings called out on each plan. New sign-ups who pick annual go straight to annual checkout.

Already on a monthly plan? Open Billing and use “Switch to annual billing” to move over (or back to monthly) — your plan’s limits stay exactly the same, only the billing cadence changes.

Reports can now post straight to a Slack channel. Connect a workspace, pick one channel, and every report arrives as a formatted message with severity, type, and description up top and the screenshot threaded underneath.

If the same app is also connected to GitHub, Jira, or ClickUp, the message links to the ticket each report created — so triage starts in Slack, and the tracker stays the record.

Testers can now tap a screenshot thumbnail in the bug-report screen to open the capture full-screen. Swipe between attachments, and delete the wrong one right from the preview — so a bad capture gets caught before the report is filed, not after. Available on both the iOS and Android SDKs, with no configuration needed.

The bug-report screen now shows the BugScreen wordmark at the top on the Free plan and hides it on paid plans, so upgraded workspaces get a reporter that looks native to their app. Visibility follows your plan at runtime: upgrade and the mark is gone on the next app launch, with no SDK update or rebuild.

The Manage billing button on the Billing page now opens the secure Stripe customer portal for your workspace. Update your payment method, switch plans, download invoices, or cancel — all self-service, no need to email us, and anything you change there is reflected on your Billing page automatically.

A new Billing entry in the sidebar shows your current plan, the price you're paying, and live usage bars for apps, bug reports, and admin seats — so you can see at a glance how close you are to your monthly limit, rather than discovering it mid-test-cycle. Upgrade and manage-billing buttons are wired up for paid plans.

The app's Integrations tab now has a Test integrations button, so you can prove a connection works without waiting on a real screenshot from an SDK install.

Click it, confirm, and the console files a clearly-marked test issue in each connected GitHub repo, Jira project, ClickUp list, and Slack channel. Results come back per integration with a direct link to the created issue — or the exact error, if one failed.

You can now change your BugScreen password without signing out. Open Account settings from the avatar menu in the sidebar and enter your current and new password. Other devices stay signed in — use Sign out of other sessions on the same page to clear them.

@bugscreen/react-native now ships an Expo config plugin, so managed-Expo projects can install BugScreen without running expo prebuild. Add "@bugscreen/react-native" to expo.plugins in your app.json and run eas build --profile development: the resulting Dev Client has the native bug reporter wired in, and no ios/ or android/ folders land in your repo.

Android 1.1.0 ships the redesigned Material 3 reporter sheet — multi-screenshot capture, inline type and severity pickers, and the new dark palette.

It also fixes screenshot detection timing: detection goes live the moment you call BugScreenSDK.start(config), not at the next background→foreground cycle, so apps that initialize after a consent prompt or from a React Native bridge no longer have a dead window where nothing is captured. A new requestPermissionsOnStart option asks for the notification permission at launch rather than at the first bug report. Available now on Maven Central as app.bugscreen:android:1.1.0.

The Android and iOS reporters now show plain-language error messages — "You're offline. Connect to the internet and try again.", "Description is too long." — with the underlying technical message behind a "Show details" disclosure. Description problems surface inline when you submit, rather than silently disabling the submit button.

When a report submits but one integration fails — Jira accepts the issue, GitHub rejects it — the toast now reads "Report sent, with issues" and names which integrations failed and why, instead of pretending everything worked.

iOS 1.1.0 ships the redesigned native bottom-sheet reporter — multi-screenshot capture, inline type and severity pickers, and a dark palette that matches the redesigned Android sheet.

The SDK is now also distributed via CocoaPods alongside Swift Package Manager. Add pod 'BugScreenSDK', '~> 1.1' to your Podfile — same framework, same API, your choice of dependency manager.

Reports now fan out to ClickUp alongside GitHub and Jira. Pick a workspace, space, and list once, and every report lands as a ClickUp task with the screenshot, description, type, and severity attached.

The iOS SDK's report screen is now a native bottom sheet with multi-screenshot capture and inline type and severity pickers, matching the redesigned Android sheet for a consistent look across platforms.

Bug reports now carry up to four screenshots instead of one. Testers add extra captures inline in the reporter, and every one is attached to the GitHub, Jira, or ClickUp issue the report creates.

That's enough to show a bug as a sequence — the state before, the tap, the wrong result — rather than one frame and a paragraph describing the rest.

Bug type and severity chosen in the reporter now map to GitHub labels and Jira priority on the created issue, so your existing triage rules and saved searches just work.

The Android SDK's report screen is now a Material 3 bottom sheet, with cleaner inputs, the new dark palette, and tighter motion.

The public API is unchanged — drop in the latest version and the new UI is automatic.

Android and iOS now accept arbitrary key/value metadata via setCustomData and clearCustomData. Tag reports with the current user, feature-flag state, build flavor, or anything else your triage needs — every report from that session carries it.