Next.js License Problem

[Harry Huynh]

I use Next.js and App Router.

I took the license key from Claim License Key, and I use the Community License.

My npm dependencies are:

"@syncfusion/ej2-base": "~29.2.4",
    "@syncfusion/ej2-react-buttons": "~29.2.5",
    "@syncfusion/ej2-react-charts": "~29.2.8",
    "@syncfusion/ej2-react-dropdowns": "~29.2.8",
    "@syncfusion/ej2-react-grids": "~29.2.8",
    "@syncfusion/ej2-react-maps": "~29.2.4",
    "@syncfusion/ej2-react-navigations": "~29.2.8",
    "@syncfusion/ej2-react-splitbuttons": "~29.2.4",

I put the register license in a component to render on the client side, and I put it in app/layout.tsx like the below images:

It still displays the error like "This application was built using a trial version of Syncfusion^® Essential Studio^®. To remove the license validation message permanently, a valid license key must be included. Claim your free account"

[Deepika Arumugasamy]

Hi Harry Huynh,

Thank you for reaching out.

We have evaluated the issue you reported and understand that you are facing difficulties while registering the license in your 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.

Upon reviewing your packages shared, we noticed that the ej2-base dependency. These are sub-dependent packages and will be automatically installed with our React component packages. So, only including our React component package is sufficient.

We would like to inform you that, if we generate a key for the major version (i.e., v27.X.XX), any key generated under the major version (v27.X.XX) can be utilized for all the minor versions in (v27.X.XX). But if you want to utilize our next major version (i.e., v28.X.XX), it is necessary to generate a new license key for the latest major version. Please make sure 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.

Documentation: License key registration

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:

Register Syncfusion license key using 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, .next folder (if exists) 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

Link:  Licensing FAQ's

We hope this information helps. If you need any further assistance reach out to us.

Regards,

Deepika