-
Notifications
You must be signed in to change notification settings - Fork 993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPFx application customizer no longer works on modern Site Contents page #8550
Comments
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible. |
I'm also facing the same issue in application customizer in site contents page. In other pages it works fine but in site contents onInit is not invoking. |
The issue has been addressed and will be rolling out in the next couple of weeks. |
Hi, is there any fix that can be locally applied for existing Application Customizer projects? |
@BhargavPrasadGorakanti - no, you just need to wait until new service build is rolled out. |
Should be rolled out globally by now |
Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues |
Existing SPFx application customizer has stopped running on modern Site Contents page. Using F12 dev tools breakpoints, it seems that onInit() no longer fires on modern Site Contents page. Console shows this:
The application customizer runs correctly on other pages, including library and list view pages. This has been tested with Chrome and Edge on three different tenants, and started failing in the past few days. That error message is not there on the pages that work correctly, but they don't seem to load sitehubwebpack.js at all, whatever that is.
The text was updated successfully, but these errors were encountered: