There are three different types of reports that, while function similarly for the end-user, appear with different types on the dashboard in order to easily separate between incoming issues. All three types will reach your dashboard with the same amount of information and can be filtered so that you can look at specific types only. If one report came under a wrong type, you can later change it's type manually from the dashboard.
When the user selects "Report a bug" from the prompt options, the sent report will appear with type Bug. This type of report is primarily meant for reporting bugs that were found in the application.
Selecting "Suggest an improvement" from the prompt options will open the improvement suggestion form that your user can use to give you feedback on how you can improve the application in certain areas. These reports are shown on the dashboard with type "Improvement".
The third option in the prompt options is "Ask a question". The purpose behind this option is for users that don't quite have a bug or an idea for an improvement, but rather a question they'd like to ask you. These show on your dashboard with type "Question".
The reports (bugs, improvements, and questions) that your users submit from your app (from the Prompt Options) are sent to the bugs page of your dashboard.
With each report, you receive a plethora of details that will help you fix bugs and get more context about the comments you receive. Throughout this page, you will learn about all the information that comes in these reports, as well as any relevant APIs that you can use to customize the data that you receive, including:
- User Attributes
- Bug Report Fields
- Auto Screen Recording
- Repro Steps
- Session Profiler
- View Hierarchy
Default attributes as well as any custom user attributes that you set are automatically sent to your dashboard with all reports.
Default attributes listed in each report include:
- App version
- OS version
- App view
- Device location
- Session duration
More details about how to set custom user attributes can be found here.
The image below shows the first view that your users see when reporting a bug after invoking the SDK.
The first step of the bug reporting flow that your app users experience.
By default, your users are required to enter a valid email address to submit a bug or feedback. To allow users to submit bugs and feedback without an email, use the following method.
BugReporting.bugReportingOptions = [.emailFieldOptional]
IBGBugReporting.bugReportingOptions = IBGBugReportingOptionEmailFieldOptional;
You can also remove the email field from the UI completely using the following API.
BugReporting.bugReportingOptions = [.emailFieldHidden]
IBGBugReporting.bugReportingOptions = IBGBugReportingOptionEmailFieldHidden;
By default, your app users can submit bugs and feedback without entering a description. To require users to leave a comment before they are able to send bugs or feedback, use the following method.
BugReporting.bugReportingOptions = [.commentFieldRequired]
IBGBugReporting.bugReportingOptions = IBGBugReportingOptionCommentFieldRequired;
Your users can submit two types of attachments with any report: default Instabug attachments (files that they can select from their device) and custom extra attachments (additional files that you can attach using code).
When your app users invoke Instabug, the SDK automatically captures a screenshot of their current view. This is the default attachment that is sent with any report. Your users can annotate this screenshot by drawing on, magnifying, or blurring specific parts.
In addition, there are other attachment types that your users can choose to send with each report. All attachment types can be enabled or disabled.
The attachment options are:
- Extra screenshots
- Images from photo library
- Screen recording
This is where your users' attachments appear in each report from the bugs page of your dashboard.
All attachment options are enabled by default if they are available in your current plan.
You can customize the attachment options that are available for your users to send by passing its corresponding enum value as an argument in the following API call.
BugReporting.enabledAttachmentTypes = [.screenShot, .screenRecording]
IBGBugReporting.enabledAttachmentTypes = IBGAttachmentTypeScreenShot | IBGAttachmentTypeScreenRecording;
Here are the possible enum values.
.extraScreenShot .galleryImage .screenRecording .screenShot
IBGAttachmentTypeScreenshot; IBGAttachmentTypeExtraScreenshot; IBGAttachmentTypeGalleryImage; IBGAttachmentTypeScreenRecording;
This is where the extra attachments appear in each report from the bugs page of your dashboard.
Use the following method to add a new file attachment.
let url = URL(fileURLWithPath: "filePath") Instabug.addFileAttachment(with: url)
NSURL *url = [NSURL fileURLWithPath:@"filePath"]; [Instabug addFileAttachmentWithURL:url];
A new copy of the file at
fileURL will be attached with each bug and feedback submitted. Extra files are only copied when reports are sent, so you can safely call this API whenever files are available on disk, and the copies attached to your reports will always contain the latest changes at the time of sending.
If more than three files are attached, the API overrides the first file. The file also has to be available locally at the provided path when the report is being sent.
To clear the list of files to be attached, use the method below. This method doesn't delete any files from the local file system. It just removes them from the list of attachments for each report.
You can make any view private so that it's hidden when a screenshot is taken. This completely hides any user data; any private view will appear with a black box covering it in any screenshot automatically. To make a view private, you use the following API.
Used for Internal Testing
The main purpose behind this feature is to specifically use it for internal testing rather than on production.
You can also automatically capture a screen recording of your app up to the last 30 seconds before a report is sent. By default, this is disabled. Your users will also be prompted once the recording starts at the beginning of the session and will have the ability to remove the video from the attachments when sending the report. The auto screen recording attachment counts towards the limit of 4 attachments in total.
This is where you can find screen recordings in each report from the bugs page of your dashboard.
A limit can be set for the total duration of the auto screen recording. By default this is set to 30 seconds, which is also the maximum duration. The API for this is shown below.
BugReporting.autoScreenRecordingDuration = 30
IBGBugReporting.autoScreenRecordingDuration = 30;
If you'd like to enable or disable the auto screen recording feature, you can use the API below.
BugReporting.autoScreenRecordingEnabled = true
IBGBugReporting.autoScreenRecordingEnabled = YES;
A whole host of logs are sent with every report. These logs include:
- Console Logs: Default logs that are printed to the console when the application is running.
- Instabug Logs: Logs with different verbosity levels that you can add manually.
- User Steps: Every step the user has taken in the form of log entries.
- Repro Steps: User steps prior to the bug report grouped by view.
- Network Logs: A log of each network request.
- User Events: A manual log of actions that a user has taken.
An example of the expanded logs view in your dashboard.
Repro Steps help you reproduce a bug by displaying your users' actions in each view of your app. With each view, you will find a list of actions that tell you exactly what the user did in that view. More details can be found here.
This is enabled by default depending on your plan.
With each report, you'll receive a detailed environment profile covering the last 60 seconds before a bug or feedback was submitted. This Session Profiler includes device data like memory load and battery state. This is enabled by default depending on your plan. More details about the information contained in the Session Profiler can be found here.
This is where the Session Profiler is located in each report from the bugs page of your dashboard.
With the View Hierarchy feature, you can visually inspect each layer in your app and see all the properties and constraints of each subview so you can spot errors at a glance.
This feature is critical for investigating UI bugs as it makes the process of finding the problem and fixing it faster and simpler. For example, if you receive a report that a certain UI view is missing, you can use View Hierarchy to easily discover if the missing view is hidden behind a higher layer, out of the parent view's bounds, or missing from the window.
Any editable text or text fields will automatically be replaced with asterisks.
An example of View Hierarchy in action from a bug report in the Instabug dashboard.
View Hierarchy is disabled by default. If you need to enable View Hierarchy, you can do so as shown in the following example.
Instabug.shouldCaptureViewHierarchy = true
Instabug.shouldCaptureViewHierarchy = YES;
Enabled from SDK version 8.3.0
The View Hierarchy will only be visible for reports coming from an application running a minimum SDK version of 8.3.0.
You can add tags to the reports you receive to help you filter and triage bugs in your dashboard. More details regarding tags can be found here.
This is where report tags are located in each report from the bugs page of your dashboard.
Spot patterns, identify trends, and explore data in your bug reports with our useful analytics. Check it out below!