Customize Report Fields

This page covers the customizable content found in the reports sent to the bugs page of your dashboard and relevant APIs for your iOS apps.

Report Content

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

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
Device
OS version
App view
Device location
Session duration

More details about how to set custom user attributes can be found here.

Bug Report Fields

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.

Email Address

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]

You can also remove the email field from the UI completely using the following API.

BugReporting.bugReportingOptions = [.emailFieldHidden]

Comment

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]

You can also set a minimum number of characters as a requirement for the comments field using the API below:

BugReporting.setCommentMinimumCharacterCountForReportTypes([.bug, .feedback, .question], withLimit:3)

Attachments

Your users can submit two types of attachments with any report: default Luciq attachments (files that they can select from their device) and custom extra attachments (additional files that you can attach using code).

Luciq Attachments

When your app users invoke Luciq, 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

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]

Here are the possible enum values.

.extraScreenShot
.galleryImage
.screenRecording
.screenShot

Extra Attachments

You can also attach up to three custom files to reports, each up to 5MB.

Use the following method to add a new file attachment.

.let url = URL(fileURLWithPath: "filePath")
Luciq.addFileAttachment(with: 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.

Alternatively, you can pass data directly as bytes using the API below:

Luciq.addFileAttachment(with: data, andName: "attachment_1.log")
//Name field is optional

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.

Luciq.clearFileAttachments()

Private View

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.

view.luciq_privateView = true

Auto Screen Recording

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.

Setting Recording Duration

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

Disabling/Enabling Auto Screen Recording

If you'd like to enable or disable the auto screen recording feature, you can use the API below.

BugReporting.autoScreenRecordingEnabled = true

To use checkboxes, you need a minimum of Luciq iOS version of v12.3.0.

To use actionable user consents, you need a minimum of Luciq’s iOS SDK version of v13.2.0.

You can use the below API to add a checkbox to your bug reporting form. These checkboxes could be used to:

Ask for the user's consent without the SDK reacting to the user's answer.
Ask for the user's consent and have the SDK drop specific data based on the user's answer.

The API will help you define:

Description: Text that appears on the end-user's device.
Key: Title that appears on the dashboard.
State: Whether the user input is mandatory or not.
Default Value: Whether the checkbox is checked by default or unchecked by default.
Action Type[Optional]: If you want the SDK to drop specific data based on the user’s answer to the checkbox, add one value from the below options.
- Options:
  - dropAutoCapturedMedia: Drops all auto-captured media, without dropping the attachments that the user attached manually
  - dropLogs: Drops all captured logs, whether they were captured automatically or added by the company itself
  - noChat: Doesn't open a new chat for this specific report and disables the chat functionality on your dashboard for this repot.

BugReporting.addUserConsent(withKey: <#T##String!#>,
              description: <#T##String!#>,
              mandatory: <#T##Bool#>,
              checked: <#T##Bool#>,
              actionType: <#T#ConsentAction#>)

[LCQBugReporting addUserConsentWithKey:<#(NSString *)#>
                           description:<#(NSString *)#>
                             mandatory:<#(BOOL)#>
                               checked:<#(BOOL)#>
                               actionType:<#(LCQConsentAction)#>];

Logs

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.
Luciq 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.

More details regarding logging can be found here. Different log types are enabled depending on your plan.

An example of the expanded logs view in your dashboard.

Repro Steps

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.

Session Profiler

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.

View Hierarchy

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.

View Hierarchy is disabled by default. If you need to enable View Hierarchy, you can do so as shown in the following example.

BugReporting.shouldCaptureViewHierarchy = true

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.

Disclaimer Text

Within the bug reporting form, you can add a disclaimer text with hyperlinked text in case you'd like to redirect users to a different page in the event that they click on a specific text (for example, if you'd like to hyperlink your privacy policy).

BugReporting.setDisclaimerText("Luciq can help developers produce more quality code. [Learn more](https://www.luciq.ai) and [more](http://string-functions.com/length.aspx).")