Net version - ODS file throws "Index was outside the bounds of the array" exception

Hi there.

I’m using the latest Aspose.Cells.Net version and it throws me an exception when initializing a new Woorbook for an ODS file:

Workbook workbook = new Workbook(fileInfo.FullName);
workbook.Save(importFilePath, SaveFormat.Csv);

Exception:
at  .()
at  .()
at  .()
at  .( )
at  .( )
at  .( )
at  .(Stream )
at  .(String , Stream , LoadOptions )
at Aspose.Cells.Workbook.(String , LoadOptions )
at Aspose.Cells.Workbook…ctor(String file)

I know the code is fine because if I open the file and save it as it is the code doesn’t break.

I’m attaching the file I’m using for testing porpuses.

Search Results 202409041041.zip (25.8 KB)

@erossi,

Thanks for the sample ODS file.

After initial testing, I was able to reproduce the issue. I found an exception “Index was outside the bounds of the array” when loading the ODS file via Aspose.Cells for .NET.

Workbook workbook = new Workbook("e:\\test2\\Search Results 202409041041.ods");

We have already opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSNET-56652

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

@erossi
We are pleased to inform you that your issue (Ticket ID: “CELLSNET-56652”) has been resolved. The fix will be included in the upcoming release (Aspose.Cells v24.9) which we plan to release in second week of September 2024. We will notify you when the next release is released.

Thank you very much for your diligence. I look forward to the next release to update it in our project.

@erossi
We will notify you as soon as it is released.If you have any other questions, feel free to ask.
Thanks!

The issues you have found earlier (filed as CELLSNET-56652) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi

1 Like

I installed the latest version and I am no longer receiving the error. Thank you all.

@erossi,

We’re glad to hear your issue has been resolved with the new version or fix. Please don’t hesitate to reach out to us again if you have any other questions or comments.