Opening PPTX Document with a Modern Comment on Object Fails

Aspose.Slides Product Family
,
1

Hi support,

Opening of a PPTX document with a modern comment on an object fails with error (see below).
NB: A new document with a comment using the new button on the right comments section (add comment to doucment) it does work. Aspose version: 22.5

We are using code:

using (Presentation presentation = new Presentation(filePath))
{
    ...
}

Error:

Exception: Aspose.Slides.PptxReadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Aspose.Slides.   .(Slide )
   at Aspose.Slides.   .(Slide )
   at Aspose.Slides.   .(Slide )
   at Aspose.Slides.   .(IPresentation )
   at Aspose.Slides.   .(    , IPresentation )
   at Aspose.Slides.   .(Presentation , Stream , InterruptionToken )
   --- End of inner exception stack trace ---
   at Aspose.Slides.   .(Presentation , Stream , InterruptionToken )
   at Aspose.Slides.Presentation.(Stream , Boolean )
   at Aspose.Slides.Presentation.(Stream , Boolean )
   at Aspose.Slides.Presentation.(String , Boolean )
   at Aspose.Slides.Presentation..ctor(String file)

The code used is like below. It fails on opening the document.

using Exception: Aspose.Slides.PptxReadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Aspose.Slides.   .(Slide )
   at Aspose.Slides.   .(Slide )
   at Aspose.Slides.   .(Slide )
   at Aspose.Slides.   .(IPresentation )
   at Aspose.Slides.   .(    , IPresentation )
   at Aspose.Slides.   .(Presentation , Stream , InterruptionToken )
   --- End of inner exception stack trace ---
   at Aspose.Slides.   .(Presentation , Stream , InterruptionToken )
   at Aspose.Slides.Presentation.(Stream , Boolean )
   at Aspose.Slides.Presentation.(Stream , Boolean )
   at Aspose.Slides.Presentation.(String , Boolean )
   at Aspose.Slides.Presentation..ctor(String file)
2

@nicolashh,
Thank you for contacting support.

To help us figure out the cause of the exception, please share the following data and information:

  • presentation file
  • OS version/distribution where the code was executed
  • .NET target platform in your app
3

Hi Andrey,
Here is a file already, will add the other info tomorrow:

Presentation2 (1).pptx.zip (6.7 MB)

4

@nicolashh,
Thank you for the presentation file. I’ve reproduced the problem with loading the presentation with modern comments and added a ticket with ID SLIDESNET-43247 to our issue tracking system. We apologize for any inconvenience. Our development team will investigate this case. You will be notified when the issue is resolved.

Thanks in advance, this information will also help us test the issue in an environment similar to yours.

1 Like
5

@Andrey_Potapov Here is the additional info:

OS: Microsoft Windows 10 Enterprise Version 10.0.19044 Build 19044
.NET Framework net472

6

@nicolashh,
Thank you for the additional information. I’ve passed it on to our developers.

7

Great, thanks.
Is there already a. view on an ETA?

8

@nicolashh,
I’ve requested plans for the issue from our development team for you. We will let you know soon.

1 Like
9

@nicolashh,
The issue investigation will begin next week. Once the cause of the problem is clear, we will be able to understand the timing of its solution.

1 Like
10

Hi Andrey,
Do you already have an update on the timing of a possible fix?

11

@nicolashh,
As far as I can see, the issue is already resolved. I asked our developers to specify the version in which the fix will be added. We will let you know soon.

1 Like
12

@nicolashh,
The fix will be included in Aspose.Slides 22.6. This release will be published in the second half of June.

13

Perfect! Thank you

14

@nicolashh,
Thank you for using Aspose.Slides.

15

Hi Andrey,
In the release notes of 22.6 I don’t see 43247 mentioned as resolved? Can you please check/confirm if that was fixed in the release as mentioned above?
Thank you,
-Gerda

16

@nicolashh,
You are right. I’ve requested information about the issue from our development team. We will let you know it soon.

17

Even. if not specically called out in the release notes, the release seems to fix our issue.
Thanks!

18

@nicolashh,
We apologize for the delay in response. Our developers confirmed that the issue has been fixed in version 22.6.