General

What is Bugsee?

Bugsee is the new word in application development. No longer should you spend hours and days communicating with your users, beta testers and QA to understand what exactly they meant when they filed that bug. While it only takes seconds to report a bug, you automatically get the following vital information in the report:

  • 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 (WiFi, 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 will not show up in the video, that includes video player windows, camera previews, password fields and views specifically marked as protected.

How does Bugsee work?

Bugsee is constantly monitoring and recording the state of the system. When the bug is detected or observed, it takes the user one shake of the device or one click of a button to trigger the process of packaging and filing all the relevant data into your favorite bug-tracker. The developer gets a nice dashboard with video of the application, all the build and system relevant information, console logs, network logs and all system events.

How much does Bugsee cost?

Bugsee is absolutely free to use on up to 5 devices. Afterwards it is $99/month or more.

Does Bugsee play nice with bug trackers and collaboration tools?

Absolutely. We already integrate with the most popular tools out there (Asana, Basecamp, BitBucket, BugZilla, Clubhouse, DaPulse, FreshDesk, GitHub, GitLab, HipChat, Jira, Monday, Nozbe, Odoo, Pivotal, Redmine, Slack, Target Process, Trello, Visual Studio Team Services, YouTrack, ZenDesk and others). If your tool is not listed, contact us at support@bugsee.com, we would love to add it for you.

What platforms are supported?

You can use Bugsee to debug iOS or Android (by embedding our SDK), as well as with these products:

iOS SDK

How easy is it to integrate?

Very, you just need to add Bugsee to your project’s gradle file and add one line of code to your Application class to launch Bugsee.

What information do I get with every report?

Here is 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 (WiFi, 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, that includes camera previews, password fields and views specifically marked as protected.

How much network traffic does it consume?

None. We do not stream anything while your app is running or sleeping, the only time data is being transferred is when an actual bug or crash is being reported.

By how much will my app grow?

Our tests show that a typical IPA file that includes both arm64 and armv7 architectures grows by about 450KB when Bugsee is included. With iOS9 app thinning feature enabled, the actual size that is being delivered to the user’s device is going to be half of that (only the relevant architecture is being installed), so we are looking at about 200-250KB, but it may vary from one to release to another.

But I already have another crash reporting tool, will they conflict?

Apple allows only one crash reporting framework to be active at any given time. While we believe that Bugsee does a very good job of detecting and recovering important data from crashes we understand if you already have your tool of choice for the job, so Bugsee crash detection can be turned off with a simple flag.

Will it work with Flutter, React native, Unity or any other 3rd party apps?

Adding Bugsee directly into resulting XCode project works, but there is added value in using wrappers to extend Bugsee functionality. We have wrappers for:

What kind of console logs are being captured?

Out of the box Bugsee captures all console logs produced by your app, be it NSLog, print or os.log. It works both on iOS10 and prior versions, both in Swift and Objective-C.

Android SDK

How easy is it to integrate?

Very, you just need to add Bugsee to your project’s gradle file and add one line of code to your Application class to launch Bugsee.

What information do I get with every report?

Here is 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 (WiFi, 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

How much network traffic does it consume?

None. We do not stream anything while your app is running or sleeping, the only time data is being transferred is when an actual bug or crash is being reported.

Will it work with Flutter, React native, Unity or any other 3rd party apps?

Adding Bugsee directly into resulting Android Studio/Gradle project works, but there is added value in using wrappers to extend Bugsee functionality. We have wrappers for:

What Android version does it work with?

The SDK is compatible with all Android platforms, but will gracefully degrade its functionality depending on the Android system your app will be running on. Video recording uses MediaProjection API and thus will be disabled on Android 4.x and lower.

Privacy & Security

How do I protect sensitive information on the screen?

Bugsee is smart enough to automatically detect password and other secure fields both in the native UIKit/Android applications as well as WebKit/Chrome/Blink forms and will automatically black out these areas of the screen in the video (sensitive data will not leave the device). In some cases it might need some help to identify such views, see documentation for more details.

What if there are tokens or passwords in the network URLs?

By default Bugsee records all network traffic in the recording. You can exclude some URLs from ever being recorded by using simple masks. See documentation for details.

How do I control access to the recorded data?

You control who within your organization can view or modify recordings. The access level control is given on a per-app basis (e.g. you can have John have access to your iOS app, but not the recordings from your Android application)

User accidentally reported a bug with sensitive data included in video/network/logs, what can I do?

Deleting an issue from within Bugsee web dashboard completely wipes out all the database records and the files associated with it. It can not be restored.

How safe is the data of my users when in transit?

All the communications between Bugsee SDKs, plugins and servers are performed with strong contemprorary encryption.

Can I release my Bugsee enabled app into Appstore?

We use only public APIs and follow recommendations and best practices when it comes to privacy, so Bugsee enabled app will pass store submission reviews. There are obviously risks involved when it comes to recording user behavior and personally identifiable data, so the business answer in your particular case may differ.