SPFx solution with Graph api not working as Teams Tab (in native client)

[MaheshakaMudli]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

other (enter in the "Additional environment details" area below)

Developer environment

No response

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• Teams desktop app (native client)
• SPFx 1.11.0
• Node.js 10.24.1

Describe the bug / error

SPFx webpart with Graph API hosted as teams tab is working fine in browsers but failing in native client app and SharePoint app too. We have started facing this issue recently as it was working before. On one of our dev tenant it is working fine but not working in prod environment.

Steps to reproduce

1. Add a sharepoint page as Teams tab with SPFX webpart and graph api in it.
2. Open the tab in native client.
3. The graph api gives 403 Forbidden error.
4. On checking the network the url which throws this error is
   https://tenant.sharepoint.com/_api/Microsoft.Sharepoint.Internal.ClientSideComponent.Token.AcquireOBOToken?resource=%27ece7c1fb-fcef-4195-ae0c-65fe47a4602e%27&clientId=%27e427a6c3-f470-4c33-9af7-6b0e1fd21eda%27

Expected behavior

The teams tab with graph api should load the data in native client too.

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[VesaJuvonen]

@MaheshakaMudli - We had recently a fix rolling for this which should resolve the issue in both web and desktop client. Is this still an issue in your environment? Getting the updated status, so that we can follow up as needed. Thanks for confirming the current situation.

[patmill]

Sorry - quick update. The fix is rolling, but is not yet 100%.

[xstos]

We have a very similar issue in our corporate spfx solution. Works in browser-based teams, but not in native client. We have a different environment that works fine. We opened the developer tools console in teams native and saw this in the network tab:

https://(redacted).sharepoint.com/sites/Finance/_api/Microsoft.SharePoint.Internal.ClientSideComponent.Token.AcquireOBOToken?resource=%27api://(redacted):23340/(redacted)%27&clientId=%27(redacted)%27
Request Method:GET
Status Code:400 Bad Request

Shall we open a separate ticket?

Also, it's frustrating that these errors are swallowed in teams with no indication of what's going on. Clicking to launch our addon does nothing. Perhaps teams needs a toast notification or something to indicate errors.