SPFX 1.23.1 HelloWorld webpart not loading - Stuck on this for over 2 days.

[mightyj0young]

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
• SPFx 1.23.1
• Node.js v22.21.0

Describe the bug / error

Been trying to debug this on the workbench and on the dev toolbar, the manifest seems to be pointing to another URL.

I saw an earlier ticket on the same being completed, however I continue to be having the same issue.

"debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/build/manifests.js"

The browser seems to be ignoring the url and trying this ,
http://localhost:4321/temp/manifests.js

Any help would be greatly appreciated.

Steps to reproduce

Expected behavior

Expected to atleast show the default HelloWorld webpart

[Ashlesha-MSFT]

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

[jhholm]

Could be related, so adding my comment here. I'm also not able to get the default app customizer template working with SPFx 1.23.1 at all. It errors while loading. SPFx 1.23.0 does work.

[brayjosh]

Thank you for the advice @jhholm.

I was able to work around this by reverting the generator to the previous release (@microsoft/generator-sharepoint@1.23.0) in place of 1.23.1. The issue no longer reproduces, which leads me to believe it was introduced in 1.23.1.

#10891 mentions that no documentation is also published for this version https://learn.microsoft.com/en-us/sharepoint/dev/spfx/compatibility

[mightyj0young]

@brayjosh that worked. Appreciate it big time @jhholm, @brayjosh .

[VesaJuvonen]

Reopening this as the active issue still exists on the 1.23.1 which we are now tracking and getting fixed asap. We do apologize the confusion and any impact this might have caused. Will close this again when the issue is resolved.