SharePoint / SharePoint/sp-dev-docs

All SPFx web parts fail to load - Public CDN issues

Open
#10,727 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:bug-suspected
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

None

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
  • Edge Version 146.0.3856.62
  • Firefox
  • Chrome
Describe the bug / error

On a single tenant (so far) - we're seeing NO SPFx web parts loading at all, instead rendering a [object Object] error

Image

I'm seeing CORS errors from the the public-cdn.sharepoint.com - client reports they've seen it for the past few days,

Image

The network request looks like this

GET https://public-cdn.sharepointonline.com/<TENANT>.sharepoint.com/sites/apps/ClientSideAssets/59903278-dd5d-4e9e-bef6-562aae716b8b/modern-search-box-web-part_f7cae02a60fdd9184eb5.js

Stripping the CDN and trying

GET https://<TENANT>.sharepoint.com/sites/apps/ClientSideAssets/59903278-dd5d-4e9e-bef6-562aae716b8b/modern-search-box-web-part_f7cae02a60fdd9184eb5.js

Works just fine, initial thought was that it was related to MC1184996 but as we're seeing ...public-cdn.sharepointonline.... and not ...publiccdn.sharepointonline... I'm pretty sure it's unrelated.

Public CDN is (and was) enabled:

Image Image
Steps to reproduce

No clue, be on an unfortunate tenant I guess, tenant is set to "Standard Release" and Data Location is "European Union\EFTA"

Expected behavior

Web parts should load 🤷

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.

Research direction

Start with the public-cdn.sharepointonline.com network request and its CORS error, then compare it with the direct tenant SharePoint URL shown in the report. Check whether the affected tenant and CDN configuration can reproduce the failure across Edge, Chrome, and Firefox. Done means SPFx web parts load normally through the public CDN; the issue names no repository files or tests.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.