We implemented Aspose.Email to read emails from the Graph API Inbox.
When we examine the code block below, we can see that the emails are successfully retrieved from Graph API — the response status code is OK, and the mails are fetched correctly from Graph API.
However, Aspose throws an internal error while parsing these emails.
We tested this issue with versions 25.9 and 25.8, and both produced the same error.
In version 25.7, there was no internal parsing issue.
var folder = client.ListFolders().First(x => x.DisplayName == “Inbox”);
var messageInfos = client.ListMessages(folder.ItemId);
on ListMessages function this error is being thrown
System.Runtime.InteropServices.COMException: 'Graph List exception: AsposeBadServerResponceException: Operation failed.: Object reference not set to an instance of an object.
Details: …
It appears you are encountering an internal error when using Aspose.Email to parse emails retrieved from the Graph API in versions 25.8 and 25.9. Since this issue does not occur in version 25.7, it may be related to changes or updates in the newer versions.
To troubleshoot this issue, consider the following steps:
Check for Updates: Ensure you are using the latest version of Aspose.Email, as there may have been bug fixes or improvements since version 25.9.
Review the Error Details: The error message indicates an Object reference not set to an instance of an object. This typically suggests that there may be a null reference in the data being processed. Review the email data being fetched to ensure it is complete and correctly formatted.
Debugging: Implement logging to capture the exact point of failure. This can help identify whether specific emails or data structures are causing the issue.
Fallback to Previous Version: If the issue persists and is critical, consider reverting to version 25.7 until a fix is confirmed in a later release.
Contact Support: If the problem continues, reach out to Aspose support with detailed information about the error and the context in which it occurs.
For further assistance, you may find it helpful to check the Aspose forums or documentation for similar issues reported by other users.
@Professionalize.Discourse
Please let us know once the issue has been resolved in the specified versions, so that we can proceed with our version update as well, since version 25.7 does not fully meet our implementation requirements.
Thank you for bringing this to our attention.
We’ve logged this problem in our issue tracking system for further investigation.
We’ll keep you informed as soon as there’s an update available.