Manual invocation

Report view

In addition to detection of shake gesture or launching with notification bar item, report view can be trigger programmatically:


// or pre-fill some fields, user will be able to modify them
Bugsee.showReportDialog("Pre-filled summary", "Pre-filled description", IssueSeverity.Blocker);

Issue create

You can build your own custom UI for collecting summary, description and severity from a user and use the following call to send resulting report to Bugsee.

Bugsee.upload("Upload summary", "Upload description", IssueSeverity.High);

Note: You should not use it for reporting errors automatically from within code, use non-fatal errors for this instead.

If you want to stop recording before showing custom report UI, it can be done the following way.

// Stop recording.

// Get report to fill.
ExtendedReport report = Bugsee.createReport();

// Fill report in a custom UI.
report.setSummary("UI is broken");
report.setDescription("It happened when I pressed the button.");
Bitmap screenshot = report.getScreenshot();
// Annotate screenshot.
report.setScreenshot(screenshot); // Call this method if screenshot was changed somehow.
// You can also add custom attributes to a report.
report.setAttribute("attr1", "attr1 value");
// ...

// Upload formed report.

// Relaunch Bugsee.
Bugsee.relaunch() // to relaunch with default options.
HashMap<String, Object> options = new HashMap<String, Object>();
// Set custom options.
Bugsee.relaunch(options); // to relaunch Bugsee with custom options.

Non-fatal exceptions

It is possible to report non-fatal exceptions from code. These reports will get combined similar to crashes, and you will be provided with statistics and a break down by unique devices, Android versions, etc.

try {
    // Code, which can throw exception.
} catch(Exception e) {