What’s new in BugScreen

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 added 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. Head to the pricing page and flip the new Monthly / Annual toggle — annual plans are billed once a year at a discount, shown as the per-month equivalent with the savings called out on each plan.

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. New sign-ups who pick annual on the pricing page are taken straight to annual checkout.

Reports can now post straight to a Slack channel. Connect a workspace, pick one channel, and every report arrives as a formatted message — severity, type, and description up top, with the screenshot threaded underneath. If the same app is also connected to GitHub, Jira, or ClickUp, the Slack message links to the ticket each report created, so triage starts in Slack without leaving the conversation.

Testers can now tap a screenshot thumbnail in the bug-report screen to open it full-screen and check the capture before submitting. Swipe between multiple attachments, and delete the wrong one right from the preview. Available on both the iOS and Android SDKs — 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 disappears on the next app launch, no SDK update or rebuild required.

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. Any change you make 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, integrations, and seats — so you can see at a glance how close you are to your monthly limit. Upgrade and manage-billing buttons are wired up for paid plans.

You can now send a test bug report to every connected integration straight from the app's Integrations tab — no need to wait for a real screenshot from an SDK install.

Click Test integrations, confirm, and the console will file a clearly-marked test issue in each connected GitHub repo, Jira project, and ClickUp list. Results appear per integration with a direct link to the created issue or a clear error message if anything failed.

You can now change your BugScreen password without signing out. Open Account settings from the avatar menu in the sidebar, enter your current and new password, and you're done. Every other signed-in session is signed out automatically.

@bugscreen/react-native 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, run eas build --profile development, and the resulting Dev Client has the native bug-reporter wired in — no ios/ or android/ folders added to your repo.

This is the release that ships the redesigned Material 3 reporter sheet with multi-screenshot capture, inline type and severity pickers, and the new dark palette.

It also fixes a long-standing footgun: screenshot detection now goes live the moment you call BugScreen.start(config) — no more waiting for the next background→foreground cycle before reports can be captured. This matters most for apps that initialize the SDK after a consent prompt or from a React Native bridge. A new requestPermissionsOnStart config option also requests the notification permission proactively at launch, instead of waiting for 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 — "We couldn't reach BugScreen, check your connection", "Your description is too long" — with a "Show details" disclosure for the underlying technical message. Description validation also surfaces inline as you type instead of silently disabling the submit button.

When a report submits but one of your integrations fails (e.g. Jira accepts the issue but GitHub rejects it), the success toast now says "Report sent, with issues" and lists which integrations failed and why, instead of pretending everything worked.

This is the release that ships the redesigned native bottom-sheet reporter with multi-screenshot capture, inline type and severity pickers, and a dark palette that matches the redesigned Android sheet.

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

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

The iOS SDK reporter 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 can now include up to four screenshots instead of one. The reporter lets users add additional captures inline, and every screenshot is attached to the resulting GitHub, Jira, or ClickUp issue.

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

The Android SDK reporter has been rebuilt as 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.

Attach arbitrary key/value metadata to bug reports with setCustomData and clearCustomData. Useful for tagging reports with the current user, feature flag state, build flavor, or anything else your triage workflow needs.