We have recently applied the latest license keys to our servers for our applications - however where the version of the library is old (version 20.8) we are getting the “Evaluation License” message even though Aspose is now licenced. Obviously we should upgrade to a later version which we will endeavor to do - but is there a way to disable this so people are not impacted until we have had a chance to update the libraries and in some cases the code which uses Aspose.
We have previously not had this issue when applying the new license files so it was a surprise.
Thank you
It seems that you are encountering an issue with the “Evaluation License” message when using an older version of the Aspose library (version 20.8) after applying the latest license keys. Unfortunately, there is no direct way to disable this message in older versions of the library. The best course of action is to upgrade to a more recent version of the Aspose library, as newer versions are designed to handle licensing more effectively.
In the meantime, here are a few suggestions to mitigate the impact on your users:
-
Error Handling: Implement error handling in your application to catch and manage licensing exceptions gracefully. This way, you can provide a user-friendly message or fallback functionality while you work on upgrading the library.
-
User Communication: Inform your users about the temporary issue and assure them that you are working on a solution. This can help manage expectations and reduce frustration.
-
Testing: Once you upgrade to a newer version, thoroughly test your application to ensure that the licensing is applied correctly and that all features work as intended.
For more detailed guidance on applying licenses and handling exceptions, you may want to refer to the Aspose documentation on licensing for Java libraries, which provides comprehensive instructions and best practices.
If you have any further questions or need assistance with the upgrade process, feel free to ask!
How many versions “back” does the issue occur on - so we know how to avoid this issue in future?
It seems you are using new license with older Aspose libraries versions. You need to use newer version of the API with newer license and use your older license to work with older APIs versions. Alternatively, you may request SHA1 encoded license (copy) from Aspose.Purchase section or sales category. Please note, newer licenses are signed with SHA256 but older ones were signed with SHA1. You cannot use a SHA256 license with older versions of the APIs (which is older than 2/3 years or so). You may use your older license to work with older Aspose versions and use new license to work with newer Aspose versions. This scenario will always work.
You can go either way (as proposed above). Let us know if we can be of any further help.