License key problem

[Shadi Bahrami]

Hello, I claim a lisence key, I have some questions:
why every time I open the claim lisence key tab in my dashboard the key changed?
Also I have these packages:

"@syncfusion/ej2-base": "^26.1.37",

        "@syncfusion/ej2-data": "^26.1.42",

        "@syncfusion/ej2-icons": "^26.2.10",

        "@syncfusion/ej2-react-base": "^26.1.35",

        "@syncfusion/ej2-react-buttons": "^26.1.35",

        "@syncfusion/ej2-react-calendars": "^26.1.40",

        "@syncfusion/ej2-react-dropdowns": "^26.1.40",

        "@syncfusion/ej2-react-grids": "^26.1.40",

        "@syncfusion/ej2-react-inputs": "^26.1.40",

        "@syncfusion/ej2-react-kanban": "^26.1.35",

        "@syncfusion/ej2-react-popups": "^26.1.41",

        "@syncfusion/ej2-react-schedule": "^26.1.41",

        "@syncfusion/ej2-react-treegrid": "^26.2.10",

why my lisence key for version 26 doesn't work?I put this on layout.js

import { registerLicense } from "@syncfusion/ej2-base";

registerLicense('lisence key');

you said in other forums that we should remove  "@syncfusion/ej2-base": "^26.1.37", from our packages is it right?
and if we remove it how could we import register License? 
I use Next js.
thanks in advance

[Mohamed Imran Thamin Ansari]

Hi Shadi,

Thank you for reaching out to us.

We have evaluated the reported issues and found a version conflict in the package.json file. If you are using a version like (26.1.X), you should use the same major version for all the Syncfusion components in your application, and the license key generated under 26.X.XX can be used for registration. However, you cannot use 26.1.XX and 26.2.XX of our components in the same application; this will create version conflicts and lead to duplication of packages, which result in license validation errors.

Yes, it is right about ej2-base; please remove any non-react packages, which are sub-dependent packages and will be automatically installed. Please find the documentation below:

 
License issue due to including non-React packages in the dependencies
 

Note: 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. Here is the modified dependency.  

        "@syncfusion/ej2-react-buttons": "~26.1.35",

        "@syncfusion/ej2-react-calendars": "~26.1.35",

        "@syncfusion/ej2-react-dropdowns": "~26.1.35",

        "@syncfusion/ej2-react-grids": "~26.1.35",

        "@syncfusion/ej2-react-inputs": "~26.1.35",

        "@syncfusion/ej2-react-kanban": "~26.1.35",

        "@syncfusion/ej2-react-popups": "~26.1.35",

        "@syncfusion/ej2-react-schedule": "~26.1.35",

        "@syncfusion/ej2-react-treegrid": "~26.1.35",

Please 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 and delete .cache from the node_modules.
   
• Update our packages to maintain same version as illustrated above.
   
• Run the ‘’npm install” command to install the Syncfusion packages again.

 

Please refer our below documentation licensing FAQ's

Link:  Licensing FAQ's

Regards,
Mohamed