SPFx Teams tab initial load not working - refresh needed

[mdanielcristian]

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

Windows

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

• browser version: Chrome 148.0.7778.169
• SPFx version: 1.22.2
• Node.js version: 22.22.0

Describe the bug / error

An SPFx web part configured as a Microsoft Teams channel tab fails to load in Teams web (and desktop client) after a full browser page refresh. The tab remains blank/stuck and the expected SharePoint-hosted SPFx iframe does not load. If the user right-clicks the tab and refreshes only the tab, the same app loads successfully.

This is an app that is deployed in production since 2021 and we made no changes to the teams app manifest or to the webpart manifest recently.

Steps to reproduce

1. Add a SPFx webpart as a tab in a Team using the web version of teams
2. Full refresh the browser window
3. Go to the previously added tab
4. The tab doesn't load, a blank page is displayed indefinitely. If I right click the MS Teams tab and refresh it, it loads

Network tab:

Console warnings that appear when clicking on the tab first time after a refresh:

Expected behavior

The tab loads without requiring a refresh.

[Ashlesha-MSFT]

Hello @mdanielcristian
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@mdanielcristian,
We were able to reproduce this issue on our end. The SPFx Teams tab indeed fails to load on a full browser refresh and only recovers after a tab-level refresh.

We will be raising a bug with the engineering team to investigate and work on a fix. Thank you for the detailed repro steps and network/console screenshots — they were very helpful in validating the issue.