Hi,
We are currently using Aspose v 18.3.0 on a .NET framework 4.6.1 application and have recently renewed the license for the same.
However, the execution stops at the SetLicense method, throwing an exception with the message '‘Invalid license signature. Please make sure the license file was not modified’.
When trying with version 21.3.0, the renewed license works fine.
I observed a similar forum that discussed this problem that mentions about updating the aspose version for the license to work, 'Invalid license signature' Exception is thrown When Aspose.Words for .NET License is Set
We are keen on sticking to the same version. Is it possible to load the license file using Aspose v 18.3.0 (by trying to modify the license file)?
If it’s not possible, which would be the version as close o 18.3 that we have to upgrade to in order for the license to work?
We have a couple of other Aspose licenses and facing a similar issue there as well.
@riteshagicha
Can you please share your license file with us in a private message? We will test it in our environment and address the issue accordingly.
Please also share, why are you not upgrading to the latest version when it is always recommended to use it. If your existing license is valid for 18.3v and you do not want to upgrade your API version, you do not need to renew your license.
We have sent you a private message and you can please share your license in .zip format while replying to it.
Hi Asad, thank you for your response.
I’ve shared the license files with you in a private message. Awaiting your reply.
Also, we tried upgrading to the latest version from v18 to v21 to make the licenses work and that created some backward compatibility issues and build errors and that is not really an option for us to update the license files, considering the expiring of the existing licenses.
Could you please let us know the way out for this case considering we’d prefer to stay on the same version(s)?
@riteshagicha
Thanks for sharing the license file in private message.
We have tested the scenario in a console application targeting .NET Framework 4.6.1 and using 18.3 version of Aspose.PDF for .NET. We did not notice any issue or exception that you have stated. A sample documented generated by using your license file is also attached for your kind reference:
test.pdf (1.3 KB)
The only versions with which this license would not work are 18.1 and lower than 18.1. And in that case, the exception message would also be different i.e. this license is not valid for this product. Please note that we changed the product name from “Aspose.Pdf” to “Aspose.PDF” after 18.1v of the API. We also added the support for older license in the higher versions of the API for those customers having licenses which were not yet expired. For example, if a license was going to expire in June 2018, it was still valid for use with 18.6v of the API even the API name was changed then.
In other words, the new license (where product name is Aspose.PDF) can only be used with the version 18.2 or higher.
Nevertheless, we tested your license file with 18.2, 18.3, 21.3 versions of the API and all test results came out fine. Please try to create a sample console application and test your license file in that application using the same method which is throwing error in your original application. If error still occurs, please share that console application with us so that we can replicate and address the issue accordingly.
It is quite possible that license file is getting corrupted in your original application due to some reasons.
Just for your information, in case your existing license is valid for the usage with 18.3 version of the API, you do not need to renew it. You can use your existing license for as long as you want in case you want to keep using 18.3 version of the API which is already supported by your existing license. You only have to renew your license if you want to upgrade to an API version which is released after the date of expiry of your existing license.
Thank you Asad. That was some really helpful information!
We created a sample console app and tried to test the license file.
LoadLicenseSampleApp.cs.zip (1.1 KB)
On testing this sample app, we observed that the Words license won’t work.
Could you please check and confirm the same?
Lastly, if we wish to remain on the same version and not renew the license, would we be deprived of any feature in the existing version(s) apart from not being able to upgrade to the new version(s)?
@riteshagicha
We need your license file in order to test it as the issue could not be replicated by using our license file in our environment. Furthermore, please post this inquiry in Aspose.Words Category where you will be assisted accordingly.
You will be able to keep using the existing API Version(s) (which is supported by your license) without any limitations and with their full capacity. In other words, no feature or existing functionality would be disturbed. However, if you intend to use any feature which was introduced in the higher/latest version of the API, you will have to upgrade the API.