-
Notifications
You must be signed in to change notification settings - Fork 1k
Open
Labels
Needs: Attention 👋Original poster responded to request for feedback, awaiting attention from Microsoft / community.Original poster responded to request for feedback, awaiting attention from Microsoft / community.area:spfxCategory: SharePoint Framework (not extensions related)Category: SharePoint Framework (not extensions related)sharepoint-developer-supportsharepoint-developer-supportsharepoint-developer-supporttype:bug-confirmedConfirmed bug, not working as designed / expected.Confirmed bug, not working as designed / expected.type:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
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 Version 119.0.6045.124 (Official Build) (64-bit)
- Edge Version 119.0.2151.44 (Official build) (64-bit)
- SPFx version 1.18.1
- Node.js version 16.20.0
Describe the bug / error
When creating a single part app page showing a custom web part, and checking the console, an error is being logged:
The error occurs in the javascript file
https://res-1.cdn.office.net/files/sp-client/sp-pages-assembly_en-us_681e18935de8c7c2ccb50e213a98d96e.js
,
Also, a warning is logged in the console:
The error and warning are not present if the web part is added to a normal page.
I could reproduce the problem in two different tenants, and using Edge and Chrome.
Steps to reproduce
- Create a web part with the Yeoman Generator with the settings:

- Create an SPFx package with the solution (no source code changes required).
- Create a communication site.
- Add a site collection app catalog to the site.
- Add the solution to the app catalog.
- Create a single part app pages containing the web part.
- Open the browser's developer tools and see the messages.
Expected behavior
No error or warning messages are being logged.
Metadata
Metadata
Assignees
Labels
Needs: Attention 👋Original poster responded to request for feedback, awaiting attention from Microsoft / community.Original poster responded to request for feedback, awaiting attention from Microsoft / community.area:spfxCategory: SharePoint Framework (not extensions related)Category: SharePoint Framework (not extensions related)sharepoint-developer-supportsharepoint-developer-supportsharepoint-developer-supporttype:bug-confirmedConfirmed bug, not working as designed / expected.Confirmed bug, not working as designed / expected.type:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.