Error moving from site page to library: Error information is 'expectingBaseExtension'.

[OmniFace]

Category

• Bug

Describe the bug

When moving between a site page and library using the left (team) or top (communication) site nav, a Client Side Extension Application Customer fails to load properly.

Steps to reproduce

Create the extension

1. Create a brand new Application Customizer

• https://docs.microsoft.com/en-us/sharepoint/dev/spfx/extensions/get-started/build-a-hello-world-extension
• Include client side assets
• Do not allow tenant deploy

2. In onInit, add a console log to verify it's successfully loading.
3. Create a production .sppkg file.
4. Upload the .sppkg to the app catalog of a SharePoint Online tenancy (I'm using First Release but I believe this happens in standard as well).

Test the extension

1. Create a modern Team site.
2. Add the extension to the site.
3. Open the developer tools Console
4. Open the site Home page
5. Verify the console message appears.
6. Click Documents in the left nav
7. Note the error:

Uncaught (in promise) Error: Failed to create application customizer 'ClientSideExtension.ApplicationCustomizer.'. Error information is 'expectingBaseExtension'.

Expected behavior

The customizer reloads properly.

Environment details (development & target environment)

The customizer does not reload properly and additional errors and issues may appear in the page depending on what the extension is expected to to.

• Your Developer Environment:

• Windows 10

• Target Environment:

• SharePoint Online

• Framework:

• N/A

• Browser(s):

• Chrome v84
• Edge v84
• Firefox v79

• Tooling:

• VS Code 1.48.0 | SPFx v1.11.0

• Additional details:

• The same issue happens with a Communication site that has the Documents library in the site nav.
• Reloading the library page or copying the URL and pasting it into the address bar properly loads the extension.
• The issue does not occur if you have a Hero web part where a tile points to the Document library.
• Moving from a library page to a site page does not trigger the issue.
• Moving from a site page to another site page does not trigger the issue.
• Moving from a library page to another library page does not trigger the issue.

Additional context

• We use the extension to provide Analytics tracking of interactions with SharePoint pages. This issue causes tracking to be lost after moving from a site page to a library, or vice versa.

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[jchilde]

I am having the same problem going from site page to list. Seems to have happened about the time the New Item button became a colored button. Simple refresh of page fixes the issue as long as you never go back to a site page.

listview-host-assembly_default_4208c255300223c76f3e1ea8ae09d6d1.js:1 Uncaught (in promise) Error: Failed to create application customizer 'ClientSideExtension.ApplicationCustomizer.f204eb2a-2d53-4086-9a77-cb1d5916bcd2'. Error information is 'expectingBaseExtension'.
at listview-host-assembly_default_4208c255300223c76f3e1ea8ae09d6d1.js:1
at async Promise.all (index 0)

[sabarinadh]

Same problem. Custom command and activates on selecting a folder or a document. Refreshing solves the problem but not all the time. Gives below error.

Uncaught (in promise) Error: Failed to create application customizer 'ClientSideExtension.ApplicationCustomizer.1a380c38-73c4-4afb-9c91-c4eba9ccda58'. Error information is 'expectingBaseExtension'.
at listview-host-assembly_default_4208c255300223c76f3e1ea8ae09d6d1.js:1
at async Promise.all (index 0)

e.prototype._createApplicationCustomizer = function(t) {
var n = this
, r = new s._QosMonitor("ApplicationCustomizer.Create");
return this._extensionManager.createExtension(t.clientSideComponentId.toString(), t.clientSideComponentProperties, function(e) {
return tt.delayExtensionsLoading ? n._applicationCustomizerContextFactory.getApplicationCustomizerContext(t) : n._applicationCustomizerContextFactory.createApplicationCustomizerContext(t, e, !1)
}).then(function(e) {
return r.writeSuccess(n._createQosExtraData(t)),
e
}).catch(function(o) {
v**ar i = new Error("Failed to create application customizer '" + t.tag + "'. Error information is '" + o.message + "'.");**
throw r.writeExpectedFailure("FailedCreateExtension", o, n._createQosExtraData(t)),
s._TraceLogger.logError(e._logSource, i),
i
})
}

[jchilde]

There was another problem related to the application customizer navigated event no firing or firing too early that prevent detection of a new page. That problem may have been fixed with the update that inserted this bug. Not sure if they are related. I have a bit more testing to do, but I am no longer seeing a problem associated with the navigated event as long as I never go to a site page.

[sabarinadh]

Our issue has to do with the list view customizer and it suddenly stopped working. Did an upgrade to the latest spfx framework and updated all outdated packages still unless you refresh the command won't launch with the error.

[OmniFace]

I am aware of an issue with navigatedEvent firing twice if you are on a Communication site and use the top nav to go to another site. I should probably file an additional defect for that, now that I've narrowed down the reproduction steps.

But as sabarinadh, this isn't about the navigatedEvent.

[andrewconnell]

SP engineering is aware of this & actively working it... will post more if/when I learn more

[OliverZeiser]

Most likely related to this issue: We are seeing that the pageContext object in our appcustomizer is not getting updated when navigating from a page to a list which breaks our solution.
Sometimes the navigatedEvent triggers twice. The second time the pageContext is correct.