License key not working properly

Question

Hi,I have in my project the following dependencies:    "@syncfusion/ej2-base": "^20.1.56",    "@syncfusion/ej2-react-buttons": "^20.1.55",    "@syncfusion/ej2-react-dropdowns": "^20.1.56",    "@syncfusion/ej2-react-gantt": "^20.1.56",    "@syncfusion/ej2-react-popups": "^20.1.55",    "@syncfusion/ej2-react-schedule": "^20.2.36",The license key worked properly (and with that I mean that the red popup was not showing up), until I added the schedule.Now the popup is showing.I tried registering a new key, which has no effect.Do you have a solution for this? It's not the first time I get this, last time I solved by using another component, but this time I have to use the scheduler.Thank you in advance,Matteo Messmer

Theveshwar Jayakumar · Accepted Answer

Hi Matteomessmer,Greetings from syncfusion support,We have
validated your reported query along with your provided details, we found that
the versions of syncfusion components are used with Cap Symbol (^) in the
package.json which leads to installation of the latest packages(v20.2.XX) in
your end instead of the (20.1.xx) packages which causes this issue, and we see
two major versions are used in components on your package.json (i.e. 20.1.XX
& 20.2.XX) which may cause some issues. So, we suggest you to use same
major version for all the components like (i.e. 20.2.XX).If you have purchased a license key for the
latest major version, (i.e. 20.1.XX), you can use the same key for all the
versions which has the same major version. There is no need to generate a new
key, for weekly releases. But, it is mandatory to generate a new license key
when you try to use different major version (i.e.20.2.XX).Kindly follow
the below steps to remove the duplicate packages and this issue will be
resolved.
 Remove the cap
     (^) symbol before the version number and use the mentioned symbol (~) before
     the version number like ("@syncfusion/ej2-react-dropdowns":
     "~20.2.36").

Delete the
     @Syncfusion folder from node_modules and the package-lock.json file from
     the root folder.

Clear npm
     cache at your end.

Run the
     ‘’npm install” or "npm install —legacy-peer-deps" command to
     install the packages.
Please
get back to us if you have any queries.Regards,Theveshwar

matteomessmer · Answer

Hi Theveshwar,Thank you very much, it worked!Best regards,Me

Theveshwar Jayakumar · Answer

Hi Matteomessmer, Thanks for the
update Please let us know,
if you have any queries RegardsTheveshwar