When using MSGraphClient on Safari non-private mode the user gets the following error on yellow bar at the top of the page. "To view the information on this page, you need to verify your identity. Click to provide additional credentials"
Expected or Desired Behavior
The MsGraphClient should not request additional credentials. This error is happening even after the user has just logged in. This only occurs in Safari. The API call works fine in IE, Chrome, and Firefox.
Steps to Reproduce
SharePoint Online
SPFx WebPart fetching data using MSGraphClient.
Example
var client = await this.context.msGraphClientFactory.getClient();
var p = new Promise<string>(async (resolve, reject) => {
let query = client
.api("/me")
.version("v1.0")
.select("displayName,mail,userPrincipalName,id");
let callback = (error: GraphError, response: any, rawResponse?: any) => {
reject(error);
} else {
// console.log(response);
resolve(response);
}
};
await query.get(callback);
});
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
Hi. It has been 4 days and no have not received a response. Any recommendations or alternatives?
@half-naan do you have a screenshot of this?
Also, need more context... what version of SPFx?
The more context details you can provide, the easier it is to help assist on issues. Any code you can provide and/or screenshots of the issue also help. The easier you can make it to reproduce the issue, the easier and quicker it is for someone to help you. Please refer to How to Create Good Issues, specifically How to Create Good Issues: Include context, in our wiki for more details.
we are using version 1.10.0 and attached is the screenshot. Thank you!

Hi. Have you guys been able to reproduce the issue? Thank you.
This only happens when prevent cross-site tracking is enabled (the default for Safari): When I disable it it works as normal. So I suspect there's a cross site cookie issue.

Has there been any progress with this?
Most helpful comment
This only happens when prevent cross-site tracking is enabled (the default for Safari): When I disable it it works as normal. So I suspect there's a cross site cookie issue.