Hi Tesnim Hamdouni,
We have evaluated the issue you reported and understand that you are facing difficulties while registering the license in your application. The invalid license key banner you are experiencing may be due to one of the following reasons: the application is registered with an invalid key, a different version of the license key or due to duplicate package installed in your application. As a result, the error message "The included Syncfusion license key is invalid." appears when launching the application.
Regarding this issue, please ensure that you are using the same major version for all Syncfusion components. Our Syncfusion licenses are version-specific, and if multiple major versions of our components are used in the same application, it can create version conflicts. Therefore, please make sure that you use the same version for all Syncfusion components.
You need to register the generated key in the application through the "register license" method, which should be called from the root folder of the application. Below is the documentation for license key registration.
And also use the ~ sign instead of ^, since it is best practice to avoid any major version upgrade conflict, and it will bring the latest patch of the current version.
You can also register the license through the npx command as an alternative approach. Please find below the documentation link for registering the license through the npx command:
Additionally, this issue may occur due to duplicate packages installed in your application. Follow the below steps to resolve the issue.
- Delete the @Syncfusion folder from node_modules and the package-lock.json file, .angular folder from the root folder.
- Clear the npm cache file at your end: npm cache clean --force.
- Update our packages to the same major version. For example, if you are using a version like (i.e., v27.1.XX), use the same version for all the Syncfusion components in the package.json file.
- Run the ‘’npm install” command to install the Syncfusion packages again.
Please refer our below documentation licensing FAQ's
If the issue persists, kindly share the package.json file and license key, so that we can provide a prompt solution
Regards,
Deepika