Skip to content

List items open to a blank page (SPListForm.aspx fails) on lists with an SPFx form customizer #11056

Closed

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

SPFx 1.23.0.

Describe the bug / error

On some of our tenants, clicking an item in a list opens a blank page instead of the form. It happens on every item in the affected lists.

These lists use an SPFx form customizer from our product. The failure happens inside SharePoint itself, before our code is ever loaded. SharePoint returns the page with the correct title, but the page body is empty and the tab title changes to “Error”. The browser never makes a request for our form customizer’s files.

We can reproduce this on our own tenant. Several of our customers see the same thing on their tenants, so it doesn’t seem to be specific to one tenant.

Steps to reproduce

  1. Open a list whose content type has an SPFx form customizer registered (DisplayFormClientSideComponentId etc.).
  2. Click any item.
  3. The browser goes to https://contoso.sharepoint.com/sites//_layouts/15/SPListForm.aspx?PageType=4&List=&ID= and shows a blank page with the tab title “Error”.

Expected behavior

When opening sharepoint list items, they load the SPFx form customizer

Activity

  1. m365-agent-toolkit-assistant commented on Oct 13, 2026

    @m365-agent-toolkit-assistant

    👋 Hi Rytis Daskevicius (@RytisDaskeviciusFlowForma),

    Thank you for reporting this issue. Here is an AI-generated initial response:

    Classification: Bug — a blank display form is inconsistent with the documented SPFx form-customizer behavior, though the cause is unconfirmed.

    • You report that SPListForm.aspx shows “Error” before requesting any customizer files. That points toward form loading rather than your rendering code, but a response trace is needed to locate the failure.
    • A related report describes Edit/View forms failing before customizer code loads on Turkish-language sites; it does not establish the same cause here.

    Upgrade check: The SPFx 1.23.2 release notes list no fix for this symptom. An upgrade from 1.23.0 is not a verified remedy.

    What to do now:

    1. Compare affected and working sites’ languages, content-type form registrations, and New/Edit/Display behavior.
    2. Capture the failing response status, browser network trace, correlation ID, and UTC timestamp; provide them to Microsoft support.

    Useful links:


    Note: AI-generated guidance may be incomplete or incorrect. Please verify suggestions before applying them.

  2. jikleveland commented on Oct 13, 2026

    @jikleveland

    We got the same problem.
    All list form customization extensions stopped working!

  3. till-llit commented on Oct 13, 2026

    @till-llit

    same issue in our PRD tenant. Test Tenant not affected.

  4. PauliusBaltrenasFlowForma commented on Oct 13, 2026

    @PauliusBaltrenasFlowForma
  5. BrunoMiculi commented on Oct 13, 2026

    @BrunoMiculi

    We have the same issue. The SPFx Workbench (_layouts/15/workbench.aspx) also shows a blank page.

  6. jusper-dk commented on Oct 13, 2026

    @jusper-dk

    We've received quite a few reports from clients about this issue this morning and have been able to reproduce it in our own tenants as well.

  7. shajumohamed commented on Oct 13, 2026

    @shajumohamed
    Contributor

    We are using Plumsail Forms to customize SharePoint list forms and are facing this issue across multiple lists as the product depend on this feature.

  8. NOC-MTA105 commented on Oct 13, 2026

    @NOC-MTA105

    Facing similar issue where Application Customizer is used for list forms. The SPListForm.aspx is failing and request response says Unauthorized in the Network tab of Developer Tools to everyone who has access.

  9. PauliusBaltrenasFlowForma commented on Oct 13, 2026

    @PauliusBaltrenasFlowForma

    10. Facing similar issue where Application Customizer is used for list forms. The SPListForm.aspx is failing and request response says Unauthorized in the Network tab of Developer Tools to everyone who has access.

    This sounds like a slightly different issue, but could be related.

  10. zapftho commented on Oct 13, 2026

    @zapftho

    As a potential correlation I also noticed that since this issue started to appear one of our Powershell scripts which uses PnP Powershell is failing now as the RootWeb and its ID can no longer be determined. In our test Tenant this is still working fine.

     Connect-PnPOnline -Url "<SharePoint Site URL>" -ClientId $env:client_id
     $site = Get-PnPSite -Includes Id, RootWeb
     $site.RootWeb.Id 
    

    Returns null in our affected Tenant.

    Not sure if its anyhow related but the timing + the fact that it works fine in the tenant that is unaffected by the Forms Customizer Issue as well, might show a correlation here.

  11. brettlonsdale commented on Oct 13, 2026

    @brettlonsdale

    Hi - we're experiencing the same issue internally and with customers.

  12. tomasz-sintel commented on Oct 13, 2026

    @tomasz-sintel

    Same with us - some clients/tenants fail to load the SPListForm.aspx contents. We cannot reproduce it locally.

  13. TMMetz commented on Oct 13, 2026

    @TMMetz

    Seeing the same behaviour here. As of now, only our test tenant appears to be affected.
    If this update is rolled out to our production tenant, it could have a significant operational impact and would likely cause major disruption.

    Update: After opening a ticket MS has confimed this Issue via SP1503038 as a recent API change

  14. 23 remaining items

  15. CDH-ADVITA commented on Oct 14, 2026

    @CDH-ADVITA

    2:00 until the next update is also unacceptable. Roll back the change and let us get back to work.

  16. SPJS commented on Oct 14, 2026

    @SPJS

    Not sure how they are rolling out the fix since I just got this error on my tenant today!

    Alexander

  17. erockwork commented on Oct 14, 2026

    @erockwork

    Looks like our tenant is working again.

    Image
  18. vladigubler commented on Oct 14, 2026

    @vladigubler

    BTW, we got first indications regarding the issue from customers around 10:00 AM EST on Monday, so it took 50 hours to handle...

  19. mgordic commented on Oct 14, 2026

    @mgordic

    30. Looks like our tenant is working again.
    Image

    I saw the same message, but so far, nothing has changed in my tenant 🤦

  20. W0ut001 commented on Oct 14, 2026

    @W0ut001

    Hmm just checked.... (21:20 CET) issue still present on our tenant.

  21. CDH-ADVITA commented on Oct 14, 2026

    @CDH-ADVITA

    Same here. we have at least a dozen reports in the last hour. At what point does Microsoft reimburse for the loss of production??? 50 hours and counting

  22. erockwork commented on Oct 14, 2026

    @erockwork

    27. Looks like our tenant is working again.
    Image

    OK, update on our tenant. Only admins of the tenant can use forms...regular permissioned users still cannot access forms.

  23. W0ut001 commented on Oct 15, 2026

    @W0ut001

    29. Hmm just checked.... (21:20 CET) issue still present on our tenant.

    It works again (7:30 CET). Had to wait a little longer than others.

  24. PauliusBaltrenasFlowForma commented on Oct 15, 2026

    @PauliusBaltrenasFlowForma

    Works on our tenants also. Took a long time to get them working again.

  25. added
    area:spfxCategory: SharePoint Framework (not extensions related)
    status:fixedIssue was fixed in current or prior release.
    and removed
    type:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
    on Oct 19, 2026
  26. VesaJuvonen commented on Oct 19, 2026

    @VesaJuvonen
    Contributor

    Seems that the root cause of this issue was the same as with #11059. The issue was detected by the automatic engineering systems, but due to internal complexity disabling the rollout of the new build took longer than expected. Engineering has acknowledged that their internal validation was missing key customer scenarios which is why this issue was not detected earlier. Needed updates are now in progress for the future testing and validation by the right teams.

    Thank you everyone for flagging the issue openly here for others to benefit - This helped to speed up the resolution of the root cause. Highly unfortunately situation which should not happen in future, given the updates on the validation processes.

    Closing this now as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

AI-generated responsearea:spfxCategory: SharePoint Framework (not extensions related)area:spfx-extensionsCategory: SharePoint Framework Extensionsstatus:fixedIssue was fixed in current or prior release.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions