Inconsistent Aspose Watermark Issue Despite Valid License (v25.7.0)

Aspose.Total Product Family
,
1

Hello,

We are currently using Aspose version 25.7.0. When generating files with an Aspose license, we’ve noticed inconsistent behavior: sometimes the output files contain an Aspose watermark, and sometimes they do not.

Could you please advise on:

  • Possible reasons why this behavior occurs?
  • Whether this is a known issue in this version
  • And if upgrading or re-applying the license would resolve the problem?

Any guidance or recommended solution would be appreciated.

Kind regards.

2

@elnur.jafar

Possible reasons for the intermittent watermark

  1. License not applied early enough – The evaluation watermark appears when an Aspose object (e.g., Pdf, Words, Cells) is created before the license is set. If some code paths instantiate the object before SetLicense is called, those outputs will contain the watermark, while other paths where the license is applied first will be clean [5].

  2. Metered‑license handling – With a metered (usage‑based) license the SDK validates the license on each request. If the validation fails for a particular request (e.g., due to a network issue or an expired token), the SDK falls back to evaluation mode and adds the watermark. This behaviour has been reported as “sometimes showing watermark” [3].

Is this a known issue in v25.7.0?
The provided sources do not contain any information about a version‑specific bug in 25.7.0 that causes random watermarks.

What to try

  1. Apply the license before any Aspose object is instantiated – place the new Aspose.*.License(); license.SetLicense(...); call at application start (e.g., in Main, Startup, or a static initializer) so that every thread sees the licensed state first [5].

  2. Verify the health of a metered license – ensure the license key/token remains valid for the lifetime of the process and that the SDK can reach the licensing server for each request. Refresh the token if it expires [3].

If the watermark still appears sporadically after these steps, please provide a minimal reproducible code snippet and details about the licensing model (perpetual vs. metered) so the issue can be investigated further.

3

@elnur.jafar,

Please note, this is not a known issue by any means. It seems your licensing code is not processed intermittently at first or you are setting the license in multi-threads. If you are using/setting your license in multi-threaded application, please make sure licensing code is processed only once and at first for the whole application life cycle. You may initialize and set the license for all Aspose APIs at application level (at the start of of your application). Please check whether the code of setting license are being executed repeatedly and concurrently, so you should place the license code at proper place and fix it on your end by yourselves. By the way, if you restart the application, does it fix the issue for a while or not?
We also suggest you to go through the documents for your reference.
e.g.,

We also recommend you to kindly create a separate console app and test your license for Aspose APIs/libraries if you find the (watermark) issue or not? If you still could not figure out your issue, please send us your license file. Please do not attach the license file with this post here. Send the license file via Email/private message. Please see the document and follow the guidelines on how to send license file for your reference:
https://forum.aspose.com/t/how-to-send-license-file-to-support-team/225542

Once we receive your license file, we will start evaluating your issue on our end.