1. Home
  2. Forum
  3. React - EJ 2
  4. ej2-react-samples repo setup

ej2-react-samples repo setup

Hi,


I am currently trying to peruse this repo locally: https://github.com/syncfusion/ej2-react-samples


I'm wondering if I am registering the license key properly, as I keep getting an error saying "The included Syncfusion license key is invalid."


Currently I have a syncfusion-license.txt set up, containing the community license key that I have. I also have a .env file containing SYNCFUSION_LICENSE. I have also ran this before gulp serve:

npx syncfusion-license activate
However the error persists. Any ideas anyone? Thanks.


Karla


1 Reply
MI Mohamed Imran Thamin Ansari Syncfusion Team August 1, 2024 04:46 AM UTC

Hi Karla,
 

Thank you for reaching out to Syncfusion Support.

 

We have evaluated your query and understand that you are facing difficulties with registering your license key in your application. Regarding this issue, please ensure that you are using the same major version for all Syncfusion components.
 

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 a license key for another platform. As a result, the error message "The included Syncfusion license key is invalid" appears when launching the application.

 

To address this, please note that Syncfusion licenses are version and platform-specific. If you are using the React application, you need to generate the key under the JavaScript platform for the version of the product you are using in your application. If you are using a version like v25.2.XX, you need to generate the key for v25.X.XX and use it in your application. Or, if you want utilize our next major version v26.1.XX, you need to generate a key under version 26.X.XX.

 

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 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., v26.1.XX), use the same version for all the Syncfusion components in the package.json file. Update the license key based on the version used.
     
  • Run the ‘’npm install” command to install the Syncfusion packages again.

 

Please refer our below documentation licensing FAQ's

 

Link:  LicensingFAQ's

 

We hope this information helps. If the issue still persists, kindly share your package.json file and your license key, so that we can provide a prompt solution.

Regards,
Mohamed Imran


Loader.
Up arrow icon