Oh, ok, I see now what's going on:
- When I write into the text field, it doesn't show when using PDF-XChange-Editor, but it shows using Adobe Acrobat Reader or any web browser (see MissingTextInPdfXChange.png)
- When I close it in Adobe Acrobat Reader, it asks to save the file although I didn't change anything.
- If I save it, the text is also visible with PDF-XChange
- The same thing happens when I open the PDF directly after it is produced by Spire.PDF for Java.
Since I can see the text in your file, I assume that you opened it in Adobe and saved it, which meant Adobe "fixed" it.
Adobe telling me to save it seems to indicate that the original PDF was not correct and Adobe does something to fix it.
But all the browsers display the "corrupt" PDF normally and I can also use Spire.PDF for .Net to read back the value inside the text field.
Thus, I think Spire.PDF produces a text field with errors which PDF-XChange handles differently than the rest of the PDF viewers and Adobe fixes the issue when saving the document.
Can you confirm that Adobe asks to save the file after it has been created by Spire.PDF for Java?
And if yes, could you maybe check with the developers if they know what this is?
According to
https://community.adobe.com/t5/acrobat-discussions/disable-quot-do-you-want-to-save-changes-before-closing-quot/td-p/9610310:
You may not have modified the document, but behind the scenes, something happened that makes the document different than it was at the time it was loaded into Acrobat. This can be either due to some JavaScript calculation in the document, or due to a problem with the PDF file that was fixed by Acrobat.
Login to view the files attached to this post.