I’m currently evaluating GroupDocs.Editor module for integration with our project and I came to this issue with corrupted document. I have downloaded your example from github (GitHub - groupdocs-editor/GroupDocs.Editor-for-Java: GroupDocs.Editor for Java examples, plugins and showcase projects) and when I call saveToWordsDocument method this exception accasionally happens (like every 3th, 4th time) for the same document (source.docx from github example):
class com.groupdocs.editor.internal.c.a.ms.System.ArgumentException: Input WordProcessing document is corrupted
on this line
InputHtmlDocument htmlDoc = EditorHandler.toHtml(inputStream);
My environment: Windows 10 64 bit, Eclipse Oxygen, Java 1.8_241
Could you please help me with resolving this exception since it’s blocker for us. I even succeed to reproduce it when it’s integrated with our project. It works only few times then suddenly throws exception couple of times and then again works two, three times, and so on (for the same document).
We’re not able to reproduce this issue at our end. Please have a look at this video. Can you please share a screencast of this issue using our console application and also share JRE and JDK versions installed on your machine.
Thanks for quick response,
I’m using java 1.8_161 but also tried with jar execution and java 1.8_241 and symptoms are the same. Here is my screencast.
We have logged this issue in our internal issue tracking system with ID EDITORJAVA-235. After further investigation we’ll notify you about the outcomes.
Is there maybe any feedback that you forgot to mention ?
I’ve also tried on several different machines and still getting the same behaviour. Also noticed that working properly with previous version GroupDocs.Editor 19.4 .
Please manually download and integrate the GroupDocs.Editor API (19.10) only from downloads.groupdocs.com. Because there is a partial fix in version 19.10 available here. So, download the API and replace it with the existing one. Hopefully, it will help otherwise this issue will be completely fixed in the upcoming release of the API.