Overview

In some situations, at end of April 2029, some customers using KWIZ Forms in full page mode were not able to load the view and edit item forms. Instead of the form, they were redirected to this error page:

Sorry, something went wrong Can't load the application on this page. Use the browser Back button to retry. If the problem persists, contact the administrator of the site and give them the information in Technical Details.Technical DetailsError details: Error: Error initializing application. Error: TypeError: Cannot read properties of null (reading 'CoAuthTenantConfiguration')Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: 1f0299a1-e0a5-8000-dfdb-176976a5f715Date and Time: 4/28/2025 12:52:19 PM

The issue targeted customers who received an update by Microsoft, and had turned on KWIZ Forms in full page mode in recent months, after Microsoft had turned off the support for custom scripts.

Customers who turned it on earlier were not affected.

Cause

An update to the SPFx framework runtime was pushed by Microsoft that caused SPFx web parts to not load if certain query string parameters were sent.

The new item form does not send those query string parameters, so it was not affected, but edit item and view item forms included an item ID parameter which seems cause the issue.

Also, the issue only happened on modern pages with SPFx components that were outside the Site Pages library, therefore customers who turned on full page mode before that were not affected, since KWIZ Forms used custom scripts to upload a page type that was not affected by this.

Status

We have logged the issue with Microsoft, and had it confirmed as a bug:

https://github.com/SharePoint/sp-dev-docs/issues/10211

Another related issue was reported after, in this bug:

https://github.com/SharePoint/sp-dev-docs/issues/10233

Microsoft had confirmed this bug, and confirmed it was rolled out to production without going through the targeted release first, thus bypassing our fast ring nightly testing which otherwise should have caught this before it affected customers.

In parallel, the KWIZ team worked hard to find a workaround and rush it through our testing, publishing it to production quickly after verifying the fix.

The fix was tested on April 29, and published to production on May 1st, as mentioned in this patch release