Single part app pages - Uncaught (in promise) error

[lucmoco]

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

1. Create a web part with the Yeoman Generator with the settings:

2. Create an SPFx package with the solution (no source code changes required).
3. Create a communication site.
4. Add a site collection app catalog to the site.
5. Add the solution to the app catalog.
6. Create a single part app pages containing the web part.
7. Open the browser's developer tools and see the messages.

Expected behavior

No error or warning messages are being logged.

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[aminezemzemi]

Hi, I encounter the same problem.
Did you resolve the problem please ?

[lucmoco]

Hi, I encounter the same problem. Did you resolve the problem please ?

No, more than one year later, I upgraded to SPFx 1.20 and the problem is still there.

[Ashlesha-MSFT]

@lucmoco,
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!