Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uniqueBody of messages is not unique #1576

Closed
mBaldasty opened this issue Sep 10, 2024 · 2 comments
Closed

uniqueBody of messages is not unique #1576

mBaldasty opened this issue Sep 10, 2024 · 2 comments
Labels
no-recent-activity status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close under investigation

Comments

@mBaldasty
Copy link

mBaldasty commented Sep 10, 2024

Describe the bug

I created a mail conversation from A to B.

A sent a message to B, B responded, A responded Back, B responded back, A responded back.

As expected the whole conversation is sent, getBody()->getContent() correctly returns all that.

I included uniqueBody in the expectation that only the new content would be present there I was wrong: Still the whole conversation is included.

Expected behavior

Only include the newest response.

How to reproduce

Just create a simple back and forth conversation between two mails and call, get the contents of the inbox loop over the mails and call

$requestConfig = new MessageItemRequestBuilderGetRequestConfiguration();
$requestConfig->queryParameters = MessageItemRequestBuilderGetRequestConfiguration::createQueryParameters();
$requestConfig->queryParameters->select = array('uniqueBody', 'bodyPreview', 'body', 'toRecipients', 'conversationId', 'conversationIndex', 'id', 'sender', 'subject', 'receivedDateTime');

foreach ($mails->getValue() as $mail) {
  $id = $mail->getId();
   $message = $graphServiceClient->users()->byUserId(_coreUser_)->mailFolders()->byMailFolderId('Inbox')->messages()->byMessageId($id)->get($requestConfig)->wait();
  Log::info($message->getUniqueBody()->getContent());
}

(using laravel here).

This is a sever bug.

SDK Version

2.13.0

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_
@mBaldasty mBaldasty added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Sep 10, 2024
@Ndiritu
Copy link
Contributor

Ndiritu commented Sep 30, 2024

Hi @mBaldasty, thanks for reporting this bug.
I'm unable to reproduce this scenario while testing on https://developer.microsoft.com/en-us/graph/graph-explorer.
Are you able to double-check that the uniqueBody is not working as expected. I don't see similar API issues created which would point to a larger problem.

@Ndiritu Ndiritu added under investigation status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Sep 30, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-recent-activity status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close under investigation
Projects
None yet
Development

No branches or pull requests

2 participants