microsoftgraph / microsoftgraph/msgraph-sdk-python

me-token-to-replace not being replaced

Offen
#1,271 0 Kommentare 2 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@ramsessanchez arbeitet bereits daran.

Seit 18.5.2026.

type:bug
Vorherrschende Sprache
Python
Sterne
630
Forks
96
Ø Merge
15 Std. 20 Min.
Gemergte PRs (30 T.)
3

Beschreibung

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!

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.