Null reference exception when converting Word doc to Pdf

Aspose Words for .Net 18.10.0.0

​sample code :

var inpfile = @"20181008-PM USA-AIR-REDACTED-NO-IMAGES.DOCX";
var outfile = @"20181008-PM USA-AIR-REDACTED-NO-IMAGES.pdf";
var doc = new Aspose.Words.Document(inpfile);
doc.Save(outfile, Aspose.Words.SaveFormat.Pdf);
StackTrace
   at  ​ ..ctor( ​  )
   at  ​ .()
   at  ​ . ()
   at    .()
   at    .()
   at    . ()
   at    .(    )
   at    .(    ,    [] )
   at    .(    )
   at    .(    )
   at    . ()
   at    .()
   at    . ()
   at    . ()
   at    .    ​(Object ,  ​  )
   at  ​ .()
   at ​  .()
   at ​  .(    )
   at    .( ​  , Boolean )
   at    .( ​  )
   at  ​ .( ​  )
   at  ​ .(    )
   at ​  .(    )
   at    .(    )
   at    .(    )
   at    . ()
   at    .(Document ,     )
   at Aspose.Words.Document.UpdatePageLayout()
   at    .    ​()
   at    .(    )
   at    .(    ,     )
   at    .(Node ,     )
   at    .(Node )
   at Aspose.Words.Document.()
   at Aspose.Words.Document.(    , SaveOptions )
   at Aspose.Words.Document.(Stream , String , SaveOptions )
   at Aspose.Words.Document.Save(String fileName, SaveOptions saveOptions)
   at Aspose.Words.Document.Save(String fileName, SaveFormat saveFormat)

We’ll be happy to renew our maintenance when this bug will be fixed.

Thanks,
Pierre

@pnocera,

Please ZIP and upload your input Word document (you are getting this problem with) here for testing. We will then investigate the issue on our end and provide you more information.

20181008-PM USA-AIR-REDACTED-NO-IMAGES.zip (3.2 MB)

@pnocera,

We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-17621. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.

ok thank you very much.

Pierre

Do you have news about a possible fix ? Our customer is waiting for it to deploy.

Thanks,
Pierre

@pnocera,

Unfortunately, this issue (WORDSNET-17621) is not resolved yet. This issue is currently pending for analysis and is in the queue. We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.

Hi,

Is it possible to have a date for this fix ?

Best,
Pierre

@pompo,

Thanks for your request. We will inform you via this thread as soon as this issue is resolved or any estimates (time frame) are available.

The issues you have found earlier (filed as WORDSNET-17621) have been fixed in this Aspose.Words for .NET 18.12 update and this Aspose.Words for Java 18.12 update.