@progress/kendo-licensing v1.5.2 - No Telerik and Kendo UI License found

[Bram]

Hello,

When updating to the latest version of kendo-licensing the license isn't applied anymore via our pipeline/site.

The step in our azure devops pipeline gives the message that the license is found but if we start our application the message comes that the license needs to be activated/watermark applied.  

With version 1.5.1 we don't have any issues. There the license is applied correctly.

Devops step:

 - script: call npx kendo-ui-license activate

      displayName: "Activate Kendo UI License"

      workingDirectory: $(ClientAppFolder)

      env:

        KENDO_UI_LICENSE: $(KENDO_UI_LICENSE)

 

Step with 1.5.2 (doesn't apply the license)

Starting: Activate Kendo UI License
==============================================================================
Task         : Command line
Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version      : 2.250.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
Generating script.
Script contents: shell
call npx kendo-ui-license activate
========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "C:\agent\_work\_temp\f68efdff-b07b-4c99-8e1f-f36fc1d33941.cmd""
[INFO][Telerik and Kendo UI Licensing] Telerik and Kendo UI License Key found at: KENDO_UI_LICENSE
  License issued at 7/2/2024 11:45:22 to ******

Finishing: Activate Kendo UI License

 

Step with v1.5.1 (does apply the license).

Starting: Activate Kendo UI License
==============================================================================
Task         : Command line
Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version      : 2.250.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
Generating script.
Script contents: shell
call npx kendo-ui-license activate
========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "C:\agent\_work\_temp\ff320d6d-9524-486a-9f27-287afe3c4338.cmd""
[WARN][Telerik and Kendo UI Licensing] No Telerik or Kendo UI product references detected in project.
  Consult the product documentation or contact support at https://prgress.co/3Pzpwvf

[INFO][Telerik and Kendo UI Licensing] Telerik and Kendo UI License Key found at: KENDO_UI_LICENSE
  License issued at 7/2/2024 11:45:22 to ****

Finishing: Activate Kendo UI License

[Sean]

We are running into the same issue today, on version 18.2. We are in the throws of trying to get this fixed, spending the whole day on it. We still have licensing issues even after downloading a new license key or reverting back to 1.5.1. Our pipeline doesn't work and we get licensing issues running things locally as well. I'll update you if I can ever get it figured out.

[Sean]

We had our package using ^1.5.1 and it was causing issues. We changed it to use 1.5.1 explicitly and we are able to get rid of the licensing issue. Fun day! 🤪

[Andrew]

Same issue here. Took 2 hours to track it down. Updated ours to 1.5.1 like Sean.

[Martin Bechev]

Hi all,

We have identified a known issue with the latest release of @progress/kendo-licensing (version 1.5.2) that may prevent proper license activation. This issue could result in the appearance of watermarks and other invalid license indicators in your application (No Telerik and Kendo UI License found error).

To resolve this issue and restore full functionality, we recommend reverting to the previous stable version (1.5.1) by executing the following command:

npm install @progress/kendo-licensing@1.5.1

After that:

1. Remove the node_modules folder, package-lock.json file and .angular folder to ensure a clean environment.

2. Rreinstall the dependencies with npm install.

We apologize for any inconvenience this may have caused and appreciate your understanding as we work to address the issue. If you have any questions or need further assistance, please don't hesitate to reach out to our support team.

Regards,
Martin Bechev
Progress Telerik