Troubleshooting

Requests are failing

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

Request	Endpoint	Detail
Config file	`https://mobile-production.content-square.net`	See Configuration
Analytics data (EU)	`https://m.csqtrk.net` `https://m.ba.contentsquare.net` `https://m.aa.contentsquare.net`	See Sending data
Analytics data (US)	`https://m-aus1.contentsquare.net` `https://m.bf.contentsquare.net` `https://m.af.contentsquare.net`	See Sending data
Monitoring	`https://l.contentsquare.net`	Used by the SDK to send SDK monitoring analysis in JSON format over HTTPS.
Session Replay data (EU)	`https://ka-aeu1.contentsquare.net` `https://ka.ba.contentsquare.net` `https://ka.aa.contentsquare.net`	See Session Replay requests
Session Replay data (US)	`https://ka-aus1.contentsquare.net` `https://ka.bf.contentsquare.net` `https://ka.af.contentsquare.net`	See Session Replay requests
Snapshot (EU)	`https://s.contentsquare.net` `https://b.ba.contentsquare.net` `https://b.aa.contentsquare.net`	See Snapshot capture
Snapshot (US)	`https://s-aus1.contentsquare.net` `https://b.bf.contentsquare.net` `https://b.af.contentsquare.net`	See Snapshot capture
Resources manager (EU)	`https://srm.ba.contentsquare.net` `https://srm.aa.contentsquare.net`	See Session Replay requests
Resources manager (US)	`https://srm.bf.contentsquare.net` `https://srm.af.contentsquare.net`	See Session Replay requests

If the following message appears in the logs:

CSLIB ℹ️ Info:⚠️ Contentsquare SDK cannot execute operation because it hasn't been started.

It means SDK API calls were done incorrectly.

In this case: gestures and lifecycle events won’t be tracked by the SDK.

Two possible explanations exist for this issue:

The SDK is manually started and API calls were made before call to start.
The SDK is automatically started and API calls were made before the AppDelegate.willFinishLaunchingWithOptions. Ensure that it doesn’t happen or contact our support team if you have a specific need.