Hi Madi,
Thank you for
reaching out to Syncfusion Support.
We have evaluated
the issue you reported and understand that you are facing difficulties while
registering the license in your next.js 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.
Also, kindly ensure
that if you are using v25 of our component, license key generated under
v25.X.XX should be used.
Note : If we generate a key for the major version
(i.e., v24.X.XX), any key generated under the major version (v24.X.XX) can be
utilized for all the minor versions in (v24.X.XX). But if you want to utilize
our next major version (i.e., v25.X.XX), it is necessary to generate a new
license key for the latest major version.
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,
which will be created inside the node_modules folder.
- Update our packages to the
same major version. For example, if you are using a version like (i.e.,
v25.X.X), use the same version for all the Syncfusion components in the
package.json file.
- Run the ‘’npm install”
command to install the node_modules.
Please refer to the
below documentation for potential Licensing Errors for further assistance.
If the issue still
persists, kindly share the complete package.json file so that we can provide a
prompt solution.
Regards,
Vijay
