microsoftgraph / microsoftgraph/msgraph-sdk-python

me-token-to-replace not being replaced

未关闭
#1,271 0 条评论 2 个 reaction 已指派 1 人 在 GitHub 查看

@ramsessanchez 已经在做这个了。

开始于 2026年5月18日。

type:bug
主要语言
Python
星标
630
派生
96
平均合并
15 小时 20 分钟
30 天内合并 PR
3

描述

I am following the same tutorial as in #544 ( https://learn.microsoft.com/en-us/graph/tutorials/python?tabs=aad ) and getting the same error. As that issue is closed, I can't re-open it. The error is that the URL used in the ultimate request includes the path component me-token-to-replace:

https://graph.microsoft.com/v1.0//users/me-token-to-replace/mailFolders/inbox/messages?$orderby=receivedDateTime%20DESC&$select=from,isRead,receivedDateTime,subject&$top=25

And the error returned by the server is:

Response content: {"error":{"code":"ErrorInvalidUser","message":"The requested user 'me-token-to-replace' is invalid."}}

I would like to know if there has been any progress on solving this or workarounds? The ticket listed in the comments is still open and it was suggested it would be fixed more than a year ago. I have used both DeviceCodeCredential and InteractiveBrowserCredential with the same error.

One of the workarounds, using graph_client.users.by_user_id instead of graph_client.me might work except I can't hardcode the user_id in the long term.

If it makes any difference, I'm running on RHEL9, Python 3.9, msgraph sdk version 1.35.0 and all dependencies the latest versions downloaded as of today. Thanks for any help!

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。