Caching issues again after uploading to app catalog

[kbeverforden]

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
#8915
#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.

[Ashlesha-MSFT]

Hello @kbeverforden,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
If you don’t receive a reply within two working days, please use this escalation form to escalate.

[Ashlesha-MSFT]

@kbeverforden,
We have successfully reproduced this caching issue with SPFx 1.22.1 on SharePoint Online. After deploying version 2.0.0 to the App Catalog, pages intermittently continue serving version 1.0.0, confirming the behavior described in this thread. We are raising this with our engineering team to determine whether a fix is feasible or if this remains expected platform behavior. We will update this thread once we receive guidance from the product team.

Thanks!