Skip to content

SPFx WebPart fails to load on Classic Page Recently with new instance. #10254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 of 9 tasks
fahadkhan85 opened this issue May 13, 2025 · 3 comments
Open
2 of 9 tasks
Assignees
Labels
area:pages Category: SharePoint Pages API relate sharepoint-developer-support sharepoint-developer-support type:bug-confirmed Confirmed bug, not working as designed / expected. type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.

Comments

@fahadkhan85
Copy link

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

  • browser version
  • SPFx version
  • Node.js version
  • etc

Describe the bug / error

Adding a new SPFx WebPart to a classic publishing page in the Pages library of a SharePoint Online site results in a runtime error. Existing classic pages with SPFx WebParts still work,new instance and old instance in Modern page still work and even the same SPFx WebPart continues to function if it was already present before the issue appeared. However, adding the same WebPart as a new instance on the same page now fails systematically.

Image

Steps to reproduce

  1. open SharePoint online classic page
  2. Edit page and add any SPFx web part which is working in same site on different/ same page
  3. Save the page.
  4. You will see the error

Expected behavior

Web part load and I should see the content.

@fahadkhan85 fahadkhan85 added the type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. label May 13, 2025
@Ashlesha-MSFT
Copy link

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

@Ashlesha-MSFT
Copy link

Ashlesha-MSFT commented May 13, 2025

@fahadkhan85,
We were able to reproduce the issue, and we are investigating it. We have logged this as a bug, and our engineering team will look into it.
Thank you for your patience!

Image

@Ashlesha-MSFT Ashlesha-MSFT self-assigned this May 13, 2025
@Ashlesha-MSFT Ashlesha-MSFT added sharepoint-developer-support sharepoint-developer-support type:bug-confirmed Confirmed bug, not working as designed / expected. area:pages Category: SharePoint Pages API relate labels May 13, 2025
@fahadkhan85
Copy link
Author

@Ashlesha-MSFT , did you find the cause or any resolution you suggest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:pages Category: SharePoint Pages API relate sharepoint-developer-support sharepoint-developer-support type:bug-confirmed Confirmed bug, not working as designed / expected. type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Projects
None yet
Development

No branches or pull requests

2 participants