SharePoint / SharePoint/sp-dev-docs

Caching issues again after uploading to app catalog

Open
#10,536 4 comments 2 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since Dec 22, 2025.

area:spfx 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?

SPFx 1.22.1

What browser(s) / client(s) have you tested
  • 💥 Microsoft Edge
Describe the bug / error

We're seeing similar caching issues again that were happening a year or two ago and fixed. After uploading to the tenant or site app catalog the new version is showing in the catalog but not being shown on sites that use it for 30+ minutes or sometimes it will show the new version and revert to the old as you click through various pages on the site. This is happening for apps that are 100 KB or 50 MB.

This makes it very difficult to release the code especially if we have APIs that are also released at the same time that do not work with the old version. Web parts are essentially broken until the new version appears on the site. This also makes it hard for our QA team to do smoke tests after releases and creates a lot of downtime that are clients are not expecting.

Let me know if there's any information I can pass along to help debug this.

Previous times this happened
https://github.com/SharePoint/sp-dev-docs/issues/8915
https://github.com/SharePoint/sp-dev-docs/issues/8803

Steps to reproduce
  1. Package solution and upload to tenant or site app catalog.
  2. Verify new version is uploaded
  3. Refresh site that contains web parts from solution.
  4. Old web parts are still showing
Expected behavior

New version should appear on sites immediately or within a few minutes.

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.