M365 - SharePoint Online - SPFx web part deployment error

M365 – SharePoint Online – SPFx component deployment issue – Error: Deployment failed. Correlation ID: 697d1d9f-000d-0000-408d-6a061a0efccf

Hi All,

Today new issue and solution 🙂

Background: My colleague created sample local tenant by joining O365 developer program , started working on SPFx component, created his first “HelloWorld” sample SPFx web part. Deployed solution at tenant level in “Apps for SharePoint” library of “AppCatalog” site but getting an error. Not getting deployed successfully 🙁

From following Fig 1, please notice that package is also valid. Also, this SPFx component get successfully deployed on my another local tenant.

Only one difference is, here “AppCatalog” site is recently created.

Error:

M365 - SharePoint Online - SPFx web part deployment error
Fig 1: M365 – SharePoint Online – SPFx web part deployment error

Deployment failed. Correlation ID: 697d1d9f-000d-0000-408d-6a061a0efccf

Unfortunately there is no clue from this error. Correlation ID changes every time when page is refreshed. No clue at all, googled a lot. Lots of developers have this issue but no exact solution 🙁

Solution: From one of the blog got a clue and it worked for us, that try to deploying the solution from the ribbon option as

 M365 - SharePoint Online - SPFx web part deployment from Ribbon menu. Get successfully deployed.
Fig 1: M365 – SharePoint Online – SPFx web part deployment from Ribbons. Get successfully deployed.

As I deployed from ribbons “Deploy” option, package get successfully deployed. I could add the web part successfully on the my sites pages 🙂

Not getting logic behind this but since it worked we proceed further 🙂

If do you already faced such issue and resolved successfully kindly please share. What resolution worked for you.

SHARING IS CARING 🙂 LIFE IS BEAUTIFUL 🙂

Advertisements

Comments

2 comments on “M365 – SharePoint Online – SPFx component deployment issue – Error: Deployment failed. Correlation ID: 697d1d9f-000d-0000-408d-6a061a0efccf”
  1. Satish says:

    Try running gulp clean before bundle and packaging the solution.

    1. Yeah tried it several time… but it didnt worked. In APp Catalog deploying from “Deploy” option from ribbon menu worked.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.