Bugsee Logo

Frequently asked questions

Can't find what you're looking for? Drop us a line at support@bugsee.com.

Contact support

General

Bugsee is the new word in application development. No more spending hours communicating with users, beta testers and QA to understand what they meant when they filed that bug. While it only takes seconds to report a bug, every report automatically includes:

  • Video of your app + user interactions (touches)*
  • Network traffic — all your API calls, with body, in one place
  • Console prints
  • CPU usage
  • Memory usage (got leaks?)
  • Active controller/view
  • Device orientation
  • Connectivity (Wi-Fi, LTE, 4G, Bluetooth, etc.)
  • System/platform version/build
  • Your application version/build
  • Crash reports with symbolication and stats
  • Custom events and traces added by you
  • 3D view hierarchy
Some views won't show up in the video — video player windows, camera previews, password fields and views you've marked as protected.
Bugsee constantly monitors and records the state of your app. When a bug is detected (or observed by the user), one shake of the device or a single button tap packages all the relevant data and files it into your favorite bug tracker. The developer gets a dashboard with the video, build and system information, console logs, network logs and all system events.
See all the details in our Pricing page.
Absolutely. We integrate with the most popular tools out there — Asana, Basecamp, BitBucket, BugZilla, Clubhouse, FreshDesk, GitHub, GitLab, Jira, Monday, Pivotal, Redmine, Slack, Trello, YouTrack, Zendesk and more. If your tool isn't listed, ping us at support@bugsee.com and we'll add it.
You can use Bugsee to debug iOS or Android natively, plus all of the following wrappers:

iOS SDK

Very. Add Bugsee to your project and call one line of code in your AppDelegate / App entry point.

Here's an ever-growing list of what we track, while keeping the promise of single-line integration:

  • Video of your app + user interactions (touches)*
  • Network traffic — all your API calls, with body, in one place
  • Console prints
  • CPU usage
  • Memory usage (got leaks?)
  • Dispatch queues delays (all five of them)
  • Active controller/view
  • Device orientation
  • Connectivity (Wi-Fi, LTE, 4G, Bluetooth, etc.)
  • System/platform version/build
  • Your application version/build
  • Crash & exception details
  • Custom events and traces added by you
  • 3D view hierarchy
Some views will not show up in the video — camera previews, password fields and views you've marked as protected.
None. We don't stream anything while your app is running or backgrounded. Data is only transferred when an actual bug or crash is reported.
A typical IPA file containing both arm64 and armv7 grows by ~450 KB when Bugsee is included. With App Thinning, what reaches the user's device is roughly half of that — about 200–250 KB. Numbers may vary slightly between releases.
Apple allows only one crash reporting framework to be active at a time. If you'd rather keep your existing tool for that job, Bugsee's crash detection can be turned off with a simple flag.

Adding Bugsee directly into the resulting Xcode project works, but our wrappers extend Bugsee's functionality. We have wrappers for:

Out of the box, Bugsee captures all console logs produced by your app — NSLog, print and os.log. Works on iOS 10 and earlier, both in Swift and Objective-C.

Android SDK

Very. Add Bugsee to your project's Gradle file and call one line of code in your Application class.

Here's an ever-growing list of what we track, while keeping the promise of single-line integration:

  • Video of your app + user interactions (touches)*
  • Network traffic — all your API calls, with body, in one place
  • Console prints
  • CPU usage
  • Memory usage (got leaks?)
  • Current activity
  • Device orientation
  • Connectivity (Wi-Fi, LTE, 4G, Bluetooth, etc.)
  • System/platform version/build
  • Your application version/build
  • Crash & exception details
  • Custom events and traces added by you
  • 3D view hierarchy
None. We don't stream anything while your app is running or backgrounded. Data is only transferred when an actual bug or crash is reported.

Adding Bugsee directly into the resulting Android Studio / Gradle project works, but our wrappers extend Bugsee's functionality. We have wrappers for:

The SDK is compatible with all Android platforms, but gracefully degrades depending on the OS version your app runs on. Video recording uses the MediaProjection API and is therefore disabled on Android 4.x and earlier.

Privacy & security

Bugsee automatically detects password and other secure fields in native UIKit / Android views as well as WebKit / Chrome / Blink forms, and blacks them out in the video — sensitive data never leaves the device. In some cases the SDK may need help identifying such views; see the docs for details.
By default Bugsee records all network traffic in the recording. You can exclude URLs from being recorded using simple masks — see the docs for details.
You control who within your organization can view or modify recordings. Access is granted on a per-app basis — e.g. John can have access to your iOS app but not the recordings from your Android application.
Deleting an issue from the Bugsee dashboard completely wipes all database records and the files associated with it. The deletion can't be undone.
All communication between Bugsee SDKs, plugins and servers uses strong contemporary encryption.
We use only Apple Public APIs and follow Apple's recommendations and best practices around privacy, so a Bugsee-enabled app will pass App Store review. There are obviously considerations around recording user behavior and personally identifiable data — the right answer for your business may differ.

Start debugging smarter today

Try Bugsee for free — no commitments, no hidden fees.

Live demoFree sign up

no credit card required