SPFx package : Upload to app catalog fails

[vipulkelkar]

Category

• Question
• Typo
• [X ] Bug
• Additional article idea

Expected or Desired Behavior

The SPPKG file should get uploaded to the App catalog without any issues

Observed Behavior

Error in uploading the file

Steps to Reproduce

Did some code changes to an existing SPFx webpart. The code builds, bundles and packages without any errors (except for a few warning of TSlint - semi colon missing). Tried to replace the existing SPPKG file of the webpart in the app catalog. Got the above error. Deleted the existing package file from the app catalog and also from the Recycle bin and tried again. still the same !

[BigEaseGueldi]

Same for me (probably everyone else). Of course this problem occurs when you are in the roll out phase of an important project. :-)

-> "we expect this process to take a few days" was not what I was hoping for ;-)

Any more specific information regarding this? @VesaJuvonen ?

[db3005]

We got the exact same issue today, also changed some code in a spfx webpart, rebuild the solution and got this error after uploading the file:

Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"Unknown Status Module: 33 Message: 134"}}}

We tried to publish the package via powershell and directly in the app catalog resulting in the same error

[vipulkelkar]

Ah !! so i missed that advisory !

[marloesdekrom]

I've got the exact same issue. Hopefully it is fixed soon.

[dlwDenysma]

Same here :( Extremely inconvenient when fixing last issues before go/no-go live...

[wictorwilen]

Same here...can't deploy...missing deadline...

[pdemro]

Same issue since Monday for us

[VesaJuvonen]

This is, unfortunately, impacting both SharePoint add-ins and SharePoint Framework solutions, like communicated in the Tenant Admin message center with the SP128660 (screenshot above). We are working on getting this resolved asap, but do not currently have an exact ETA which can be shared here.

[trillian74]

Oh lord... major demo with Statoil tomorrow and we cannot get our massive effort out on the tenant...

[BigEaseGueldi]

Wondering whether switching the "componentType" in *.manifest.json to "Library" and then load the stuff manually on a classic page would be a workaround.

[trillian74]

Any news?