Setting Custom Data for Flutter

Discussed here is how to set user attributes and tags, as well as log user events, and their relevant APIs for your Flutter app.

User Attributes

You can assign custom attributes to your users and they will show up on your Instabug dashboard with each report. These attributes can later be used to filter reports in your dashboard.

2888

This is where additional user attributes appear in your bug reports.

To add a new user attribute use the following method.

Instabug.setUserAttribute(String value, String key)

//Examples
Instabug.setUserAttribute("18", "Age");
Instabug.setUserAttribute("True", "Logged In");

You can also retrieve the current value of a certain user attribute, or retrieve all user attributes.

// Getting attribute
Instabug.getUserAttributeForKey("Logged in");

// Loading all attributes
Instabug.getUserAttributes();

Or remove the current value of a certain user attribute

Instabug.removeUserAttribute("Logged In");

User Events

You can log custom user events throughout your application. Custom events are automatically included with each report.

Instabug.logUserEvent("OnFeedbackButtonClicked");

Tags

You can add custom tags to your bug and crash reports. These tags can later be used to filter reports or set custom rules from your dashboard.

2888

This is where tags appear in your bug reports.

The example below demonstrates how to add tags to a report.

Instabug.appendTags(["Tag 1", "Tag 2"]);

You can also get all the currently set tags as follows.

Instabug.getTags();

Last, you can reset all the tags.

Instabug.resetTags();

Managing Tags

If you'd like to remove a particular tag from your dashboard to prevent it from appearing again when entering a new tag manually, you can do so by navigating to the tags page under the settings options and remove the tag. You can also edit and rename the tag.


Feature Flags

In certain scenarios, you might find that you're rolling out different experiments to different users, where your user base would see different features depending on what's enabled for them. In scenarios such as these, you'll want to keep track of the enabled experiments for each user and even filter by them.

Notes:

  1. Feature Flag Naming: Each feature flag name should not exceed 70 characters and each variant name should not exceed 70 characters. Otherwise, they will get ignored by the SDK. Note that feature flag names are case-insensitive.
  2. Feature Flag Persistence: Feature flag persist beyond individual sessions and are not automatically removed at the end of a session. Additionally, calling the logOut function does not impact the existence of the feature flag. The feature flag is only removed when you call the removing method or the clearing method.
  3. The amount of feature flags sent in a session is 200 with maximum of 1 variant per a multivariate feature flag. For example, a feature flag that has 3 variants sent within 1 session will only be sent to our backend as the last variant, and not all 3.

For more information on feature flags, visit Feature Flags.

Adding Feature Flags

Boolean Feature Flags - Example Usage

Below is an example of where in your code you would use feature flag. In this example, you are experimenting with feature logic that controls whether or not the user has a Dark Mode toggle available.

Instabug.addFeatureFlags([FeatureFlag(name: 'Boolean Feature Flag')]);

Multivariant Feature Flags - Example Usage

Below is an example of where in your code you would use feature flag with multiple variants. In this example, you are experimenting with feature logic that controls multiple versions of a specific feature.

Instabug.addFeatureFlags([FeatureFlag(name: 'Feature Flag', variant: 'Value')]);

Removing Feature Flags

If your feature flag is concluded or you would like to simply remove it, you can use this method:

Instabug.removeFeatureFlags(['feature flag']);

Clearing Feature Flags

You can use the below method to clear all the Feature Flags from your reports:

Instabug.clearAllFeatureFlags();

What’s Next

You now have more information than ever about each bug and crash report, so we suggest you read up more on bug and crash reporting.