Configuration

Launching with options

Bugsee behavior is very customizable, if default configuration is not satisfying your needs you can launch the SDK with additional parameters. You'll need to create partial class BugseeLauncher within namespace BugseePlugin in a separate file. Use instance of IOSLaunchOptions or AndroidLaunchOptions for corresponding platform to change Bugsee behavior.

namespace BugseePlugin
{
    public partial class BugseeLauncher
    {
        static BugseeLauncher()
        {
            AndroidOptionsHandler = GetAndroidOptions;
            IosOptionsHandler = GetIosOptions;
        }

        private static AndroidLaunchOptions GetAndroidOptions()
        {
            return new AndroidLaunchOptions()
            {
                // Set custom Android launch options here.
                VideoEnabled = false
            };
        }

        private static IOSLaunchOptions GetIosOptions()
        {
            return new IOSLaunchOptions()
            {
                // Set custom iOS launch options here. 
                MonitorNetwork = false
            };
        }
    }
}

Stopping

Stopping will fully stop the SDK operation and clean up all the used resources. The operation may take a while to complete.

Bugsee.Stop();
}

Relaunching

Stopping will fully stop the SDK operation and clean up all the used resources. Upon completion it will relaunch it again with new options.

BugseeLaunchOptions options = ...;
Bugsee.Relaunch(options);

Available Options

For iOS

For Android

Android video modes comparison

Built-in reporting UI adjustments

Alongside stylistic changes, you can also change the placeholders' texts shown in input controls within the built-in bug reporting UI

Bugsee.Appearance.Report.SummaryPlaceholder = "What's happened? Only shortly";
Bugsee.Appearance.Report.DescriptionPlaceholder = "Here, describe all the pains and frustrations you had. In details";
Bugsee.Appearance.Report.EmailPlaceholder = "Identify yourself here";
Bugsee.Appearance.Report.LabelsPlaceholder = "Labels.For.Developers. [Comma separated]";

**VideoMode.V2: Starting Android 9 it requires FOREGROUND_SERVICE permission. Starting Android 14 it requires additional FOREGROUND_SERVICE_MEDIA_PROJECTION permission. If you want to use V2 mode, your application will have to declare these permissions in manifest.

***VideoMode.V3: On Samsung devices, VideoMode.V3 will work only on Android 8 and up. Earlier versions of Android on Samsung devices are known to have issues when VideoMode.V3 is being used and hence it preemptively disabled there.

****VideoMove.V4: VideoMode.V4 (experimental) gives client code an ability to decide when to add frames to a video, calling Bugsee.Snapshot() method. If frames are added rarely, additional CPU and GPU load is relatively small, but the resulting video looks more like a slide show. And vice versa, in case of frequent calls to Bugsee.Snapshot() performance can be influenced essentially, but the resulting video looks better. By default frame is added to a video only on the start of recording and on exception.

Note that it is necessary to enable "Allow unsafe code" option in Player Settings and to execute an additional step, described in "Gather GPU info on Android" section of Installation guide to make VideoMode.V4 work. Also, note that starting with Bugsee Unity SDK 1.7.0 V4 is disabled and unavailable by default. You need to define BUGSEE_VIDEO_V4 to enable VideoMode.V4. The reason for this, as stated above, is that V4 requires unsafe option to be set for the project, which is not usually desired. You can find out how to supply your own #define directives in Platform dependent compilation section of Unity documentation.