We are starting with the update from our Angular 13 project to Angular 14.
After the update we get the demo version message. However the license key we used in the 13 version is still in the main.ts file. (registerLicense(xxx our key xxxx).
The SyncFusion packages are still on release 20.1.x so this registration key should still be valid.
What do I have to do to get rid of the demo version message?
Greetings from Syncfusion support,
We suspect that the versions of syncfusion components you are utilizing in your application might have Cap Symbol (^) in front of the versions in the package.json for eg:("@syncfusion/ej2-angular-calendars": "^20.1.47"). This will leads to the installation of the latest packages(v20.3.XX) on your end instead of the (20.1.xx) packages, which cause this issue.
We suggest you to follow the below steps to resolve this issue.
If the issue still persists at your end, kindly provide the issue reproducing sample, so that we can assist you to achieve your requirement.
Thank you for your response.
The ^ was indeed the issue. Everything is working fine now. Thank you very much!
We are in a transition from Angular 13 with the Syncfusion packages 20.1.x to Angular 14 with the Syncfusion 20.3.x version. So we will create a new license number for the new version of our software. Does this new license number has effect on our current license number for the Angular 13 version and the builds we are still make with the 'old' versions? With other words. Can the old and new license conflicts with each other?
Since Syncfusion license validation is version based so you must use any one version for all Syncfusion components for example if your using (v20.2.XX) same version must be used for all the Syncfusion components in your project. If you try to use the license key version having (v20.3.XX) with the version (v20.2.XX) components it will result in license mismatch and banner will appear. So to resolve this issue you need to stick to any one version for all Syncfusion components like (v20.2.XX). Also if you want to upgrade for the latest version (i.e. v20.3.XX) you need to generate a separate license key and update the package version as (v20.3.XX) in the package.json file.
Please let us know if you have any queries.
Thank you for very much for the info.
Thanks for the update.
Please get back to us if you have any queries.