logo
search
Others

Fix SPFx Application Customizer Not Running on SharePoint Site Contents

Steve KSteve K Sep 29, 2026 869 views

Question details

Users need to resolve an issue where their SPFx BaseApplicationCustomizer extension does not execute its onInit function on SharePoint Site Contents pages.

Fix SPFx Application Customizer Not Running on SharePoint Site Contents
Product
SharePoint Online
Device & OS
not provided
Scenario
Developing and deploying SharePoint Framework (SPFx) extensions across site collections.
Observed behavior
The SPFx Application Customizer fails to trigger on Site Contents pages, despite successfully loading and running on other standard SharePoint modern pages across multiple tenants.
Before you start

Ensure you have Site Collection Administrator privileges and full access to the SharePoint App Catalog before making changes to extension deployments.

Solution 1Recommended

Verify App Catalog Library Permissions

Ensure that the intended end-users have the correct read access to the App Catalog library where the SPFx package is stored.

If users lack read permissions to the specific library housing the SPFx package, the extension will silently fail to load its resources on certain system pages like Site Contents.

1
Navigate to the App Catalog

Open the SharePoint Admin Center, expand the 'More features' section, and click 'Open' under Apps to access the tenant App Catalog.

2
Check Library Permissions

Go to the 'Apps for SharePoint' library settings, click on 'Permissions for this document library', and verify that 'Everyone except external users' (or your target group) has Read access.

3
Re-test the Extension

Once permissions are verified or granted, open an incognito browser window, log in as a standard user, and navigate to the Site Contents page to confirm the extension loads.

Verify App Catalog Library Permissions
Deployment Scope: Always verify that the app is properly installed, deployed, and associated with the specific site collections where it is failing.
Free Microsoft Office alternative

Need a Lightweight Alternative for Daily Office Tasks?

While complex SharePoint development requires the Microsoft ecosystem, you do not need heavy, expensive subscriptions for your everyday document, spreadsheet, and presentation tasks. WPS Office provides a powerful, free, and highly compatible alternative.

  1. 1. Download WPS Office: Visit the official WPS website and download the free installer for your operating system.
  2. 2. Install the Software: Run the downloaded installer file and follow the simple on-screen instructions to set up the suite.
  3. 3. Open Your Documents: Launch WPS Office and instantly open your existing Microsoft Office files without losing any formatting.
Free and lightweight office suite for Windows, Mac, and LinuxHighly compatible with Microsoft Word, Excel, and PowerPoint formatsSeamless migration with a familiar, tabbed user interfaceBuilt-in robust PDF editing and conversion tools
microsoft office alternative - wps office

Frequently Asked Questions

Why does my SPFx extension work on standard modern pages but not Site Contents?

Site Contents is a system-level modern page in SharePoint. Microsoft occasionally pushes service updates that can temporarily alter how SPFx extensions load on system pages compared to standard user-created site pages.

How can I check if my SPFx package has permission issues?

Navigate to your tenant's App Catalog, open the 'Apps for SharePoint' library permissions, and confirm that your target users (or 'Everyone except external users') have at least Read access to the library files.

Does the version of SPFx affect compatibility?

Yes. Different versions of the SharePoint Framework are targeted at different environments. For example, SPFx 1.4.1 is required for SharePoint 2019, while SharePoint Online supports the latest SPFx releases. Mismatched versions can cause silent loading failures.

What should I do if a minimal test extension also fails on Site Contents?

If a newly generated, minimal SPFx Application Customizer fails on Site Contents across multiple site collections or tenants, it strongly indicates a Microsoft-side service issue. You should open a support ticket via the Microsoft 365 Admin Center.