Getting Manifest not found for component id errors when adding a custom SPFx webpart to a site

Question

Hi,

For my SP Online instance, I made a SPFx webpart and when I deploy it to a site, I get the following. I did a non-tenant wide install to the tenant app catalogue. And then I installed the app on my site, and then I added it to a page.

[SPLoaderError.loadComponentError]:
Failed to load component "79252476-fc6d-42fc-881c-0a2ff579ce10" (MyWebPart). Original error: Manifest not found for component id "d1abf378-f9bc-4bc6-9c52-17bb49c75cf1" and version "0.0.1".

INNERERROR:
Manifest not found for component id "d1abf378-f9bc-4bc6-9c52-17bb49c75cf1" and version "0.0.1".
CALLSTACK:
Error
    at t [as constructor] (https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_699158f7fea868eb081b869967788f85.js:1:862008)
    at new t (https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_699158f7fea868eb081b869967788f85.js:1:1006242)
    at Function.e.buildErrorWithVerboseLog (https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_699158f7fea868eb081b869967788f85.js:1:1046567)
    at Function.e.buildLoadComponentError (https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_699158f7fea868eb081b869967788f85.js:1:1042612)
    at https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_699158f7fea868eb081b869967788f85.js:1:1034879

The app is configured to include client side assets. Is it possible the SharePoint CDN is not configured properly?

Does anyone know what's wrong here?

Answer 1

I figured it out, it was my issue. I was using a spfx library plugin and forgot to deploy it tenant wide first.

Answer 2

Hi @Ryan ,

Does the spfx webpart work in workbench.aspx? This usually caused by your code build failed. When you run gulp serve, there would be error in node console. You could check the error and fix it.

For CDN, If Microsoft 365 CDN is enabled, it's used automatically with default settings. If Microsoft 365 CDN isn't enabled, assets are served from the app catalog site collection. This means that if you leave the includeClientSideAssets setting true, your solution assets are automatically hosted in the tenant. Please refer to this article:
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn

To verify that you have CDN configured properly, please run the command: Get-PnPTenantCdnOrigin -CdnType "Public" . Make sure you have a Public CDN origin configured for ClientSideAssets.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Actually I want it to load from the app catalogue site for now, so keeping CDN disabled is fine, I think it is disabled actually.

Also when I check on workbench.aspx, it works there.

Answer 4

I am also facing same issue while trying to run Gulp Serve on workbench for https://learn.microsoft.com/en-us/training/modules/sharepoint-spfx-web-part-property-pane/7-exercise-pnp-controls