License registration

[Marko]

Hello,

we have problems building our Vue3 project using Gitlab CI/CD platform. When we build and run application a warning is issued that included Syncfusion license key is invalid. With Local builds we never get an invalid license message.

In the CI/CD settings a variable named SYNCFUSION_LICENSE is declared with the license key value.

Our build script has following entries

Please provide advice.

Kind regards,

Marko

Attachment: Variable_c098c8b8.png

[Deepika Arumugasamy]

Hi Marko,

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. 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.

 

In your production environment, instead of registering license through environment variable you can register the Syncfusion license in text file and activate through npx command. Please ensure that the Syncfusion license is activated before the build process by following these steps:

1. Create a license text file:

   • In the application root directory, create a file named syncfusion-license.txt and paste your Syncfusion license key inside it.

2. Activate the license key:

   • Open a command prompt in the application root directory and execute:

     npx syncfusion-license activate
     

     
     

3. Verify activation:

   • Once the license key is activated, you should see the following console message:

     (INFO) Syncfusion License imported successfully.
     




4. Run the application:

   • Restart your application

Please find below the documentation link for registering the license through the text file and npx command and registering license in CI service:

License key registration in Vue Licensing component | Syncfusion

License key registration in Vue Licensing component | Syncfusion

Please refer our below documentation licensing FAQ's

 

Link:  Licensing FAQ's

 

If the issue persists, kindly share the package.json file and license key, so that we can provide a prompt solution.

 

Regards,

Deepika

[Marko]

Hi Deepika,

thank you for the reply. The proposed solution requires that the license file be committed to the version control which is not something we would not like to do.

I do not think we have a license problem because as I said in my original post we have no problem building locally, problem is with the GitlLab CI/CD.

One additional note, using the 'npx syncfusion-license activate' in the CI/CD script produces '(INFO) Syncfusion License imported successfully.' in the buiild log, but when the app is run there is a message about invalid license displayed.

So to summarize could you provide instructions for the GitLab CI/CD platform.

I am sharing the package.json and I can share the license key also just advise how to do it in a secure way.

Kind regards,

Marko

Attachment: package.json_ce91bf72.txt

[Deepika Arumugasamy]

Hi Marko,

We apologize for the inconvenience.

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 the packages shared, we noticed the multiple major version used for Syncfusion Vue packages. Kindly update the Syncfusion Vue packages to the same major version. If you are using a version like 27.1.X, it is important to use the same version for all Syncfusion components in your application. The license key generated for version 27.X.XX can be used. This key can be used across all minor versions within that major version, v27. This means you can upgrade all packages to 27.2.X while still using the same license key. 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.

 

The ^ symbol allows for major version upgrades, which can sometimes lead to conflicts. To avoid this, we recommend replacing 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.

 

Additionally, we suspect 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., 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

[Marko]

Thank you for the assistance.

Marko

[Archana Jayakumar]

Hi Marko,

You're welcome! please get back to us if you need any further assistance.

Regards,
Archana