Troubleshooting

This section provides pointers to help you solve issues you can run into the Flutter SDK.

For sessions to be tracked:

• A first screenview has to be sent
• The current user has to opt-in to have their actions tracked

Contentsquare SDK is not compatible with hybrid applications.

In-app features requires a specific configuration on iOS.

Contentsquare SDK uses zoning identifier that relies heavily on the structure of the widget tree. Changes to the widget tree such as moving, nesting, or removing a widget may result in the loss of tracking data.

The Contentsquare Flutter SDK provides the ReliableTarget widget, designed to encapsulate the widget intended for reliable tracking.

A common mistake is to trigger the sending when the confirmation screen is displayed. This leads to triggering the transaction each time the user puts the app in background and then in foreground on the confirmation screen.

By default, the ContentsquareRoot widget masks all types of content (texts, text fields, and images) during replays. It achieves this by providing a default MaskingConfig object if none is specified.
The default configuration masks everything, ensuring that sensitive information is protected.
However, you can override the default masking behavior by providing your own MaskingConfig object when creating a ContentsquareRoot widget. This allows you to customize the masking rules for your app according to your requirements. See MaskingConfig for more information.

The masking / unmasking of Session Replay through the in-app features settings is not yet supported by the Flutter SDK.

This setting is intended for debugging purposes only. See MaskingConfig for more information.

Put your app in background to trigger the sending of the session to the server.
Session Replay is not instantaneous and takes from 5 minutes to 30 minutes to be available.

For Session Replay to work, sessions must be tracked:

• A first screenview has to be sent
• The current user has to opt-in to have their actions tracked

There is no collection of the user’s screen, but rather a reconstruction interactions based on the data collected by the SDK.
The rendering may not be pixel-perfect, but it should give you a good idea of how users interact with your app. There are some known limitations to the Session Replay feature.

If you notice a limitation that is not referenced in our documentation, contact us.

If you struggle to watch a replay collected on an emulator/simulator, it may be due to some network constraints applied on your computer (VPN, company network restrictions, etc.). Check your configuration and/or use a real device.

For more information about our endpoints and requests, see:

• Android - Requests are failing
• iOS - Requests are failing

It is important to remember that an app kill does not end a session.
See Session definition for more information.

If you leave the simulator/emulator running with the app in foreground, the session will not end, even if you are inactive. To better reflect actual end user behavior and avoid unusually long sessions (last hours), put the app in background or kill it.

During the initialization, the Contentsquare SDK overrides the HttpOverrides.global property.

Avoid overriding HttpOverrides.global in your app.
If you have to, see Use a custom HttpOverrides.

There is a known issue with the background_locator ↗ plugin which causes Contentsquare plugin to be registered twice. This issue has been mitigated and you can ignore this warning.

If you are not using the background_locator plugin and encounter this warning, contact us.

In order for Contentsquare to work, you need to make sure the following endpoints are not blocked by your network (VPN):