SharePoint / SharePoint/sp-dev-docs

SPFx Teams tab initial load not working - refresh needed

Open
#10,866 3 comments 1 reaction 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since May 27, 2026.

area:spfx-msteams sharepoint-developer-support type:bug-confirmed
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

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:
Image

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

Image
Expected behavior

The tab loads without requiring a refresh.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.