Here are some common bugs encountered when integrating Clice:

1. Package version

Make sure you’re using the latest version of the package in your frontend. Check current versions here: Versions.

2. After frontend integration, 403 error in the console

This happens when your domain is not authorized to send a request to your Clice application.

Solution

In the Clice settings popup, open the Domains section and add the domain of the site where you want to integrate Clice.

Make sure you use the correct format:

protocol://domain_or_subdomain.extension

For example, to integrate on Clice’s back office, I authorized:

• https://my.clice.app
• https://www.my.clice.app

3. Error when signing the token in the initialization route

The most common cause is either forgetting the private key or having spaces in it, which causes the token signature to fail.

Solution

Make sure your private key is correctly defined and properly formatted, with its header and footer intact, no extra spaces, and correctly separated lines.

For example, to integrate Clice into Clice itself, I used this function to fix a malformed private key (originally stored as a single-line string with line breaks replaced by spaces):