0

I have deployed a SPFx Extension solution to my site.

Everything went well except the Extension sometime loads, sometimes doesn't. In another word, if I refresh it a few times then sometime it won't work.

All I got in the browser console when it doesn't work is: 

Failed to create application customizer 'ClientSideExtension.ApplicationCustomizer.6998cb93-00a1-46a6-a00b-786fd612c706'. Error information is '***Manifest not found for componentId "6998cb93-00a1-46a6-a00b-786fd612c706".'

I know the manifest is there since it's working with some refresh. The scripts are deployed into our CDN in the same site collection.

enter image description here

Elements:

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">    
<!-- Custom Action -->
<CustomAction 
    Title="SpFxTermsConditionsApplicationCustomizer"
    Location="ClientSideExtension.ApplicationCustomizer"
    ClientSideComponentId="6998cb93-00a1-46a6-a00b-786fd612c706"
    ClientSideComponentProperties="{&quot;Top&quot;:&quot;Top area of the page&quot;,&quot;Bottom&quot;:&quot;Bottom area in the page&quot;}">
</CustomAction>
<!-- End Custom Action -->

Can someone know what cause this ? Thanks,

Improve this question
5
  • 1
    make sure you have the correct versions of tools. This was a bug a while back but has been fixed: github.com/SharePoint/sp-dev-docs/issues/632
    – Ali Jafer
    Commented Oct 9, 2017 at 11:01
  • can you also share the elements.xml file ? Did you reference that file correctly in the ` package-solution.json` file ?
    – Gautam Sheth
    Commented Oct 9, 2017 at 12:47
  • @AliJafer: I'm running latest SPFx 1.3 but I'll check tmr to see if it's updated or anything else is outdated.
    – Thi Vo
    Commented Oct 9, 2017 at 16:38
  • @GautamSheth: I will post it tmr. But if it's incorrect then it shouldn't work at all. Not like this. This is weird T_T
    – Thi Vo
    Commented Oct 9, 2017 at 16:40
  • @AliJafer: I updated the @types/sharepoint to latest version and things seem to work normally again (the types was update 3 days ago)
    – Thi Vo
    Commented Oct 10, 2017 at 4:01

1 Answer 1

Reset to default
0

Update @types/sharepoint into 2016.0.0 fix it.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.