Sp-dev-docs: 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?

[VesaJuvonen]

@trillian74 there is internal progress on getting this resolved, but we can't give yet exact ETA.

[dougraheem]

Same issue. I bang my head against the wall over and over . Then found out there is an advisory. Interestingly, my developer tenant does not have an SharePoint Online Advisory but production tenant does. I believe issue is happening across all tenants.

[Christian-Stahl]

Same here. Hope it will work soon, at least we got our workbench to play with in the meantime :)

[dougraheem]

Use hosted workbench to in case web part is list data driven :)

[tdwhite0]

Surprised this is not getting more attention, its a pretty big showstopper.

[jonathanhotono]

I got the same issue too.

[rgarita]

Just to add more pressure,, We are being also impacted by this issue. an ETA will be appreciated....

[michel-weber]

Same here: All our automated deployments fail on all tenants (3).

We also tried to manually upload and it fails.
We are just lucky that we don't have any important rollouts just now.

I'm wondering why this is not covered by automated regression tests? As stated in the advisory, it is a coding error so this could have been prevented.

I really hope that after this is resolved, steps are taken to prevent this to happen again.

Great work on all the features of the tenant and site collection app catalogs btw ... we use the ALM APIs to deploy (before I automated everything by using Selenium).

[VesaJuvonen]

Thanks everyone for your input on your observations. We are working hard to get this resolved worldwide asap. We will also make changes in our validation process for the future to minimize possibilities for similar issues.

Thanks, @michel-weber also for the feedback on the latest capabilities, always appreciated. We, unfortunately, cannot give exact ETA at this point world world-wide resolution.

[wictorwilen]

I can confirm that it is now working properly again on a few of my tenants

[michel-weber]

I can also confirm - it is working properly again on at least one of my tenants (SPFx deployment).

[BigEaseGueldi]

Jup, works again. European tenant.

[dlwDenysma]

Yes, working again! 👍

[VesaJuvonen]

Thanks for your status updates. The fix is being rolled out gradually cross tenants. We do not have an exact ETA for the fix being 100% available worldwide, but you will see tenants getting fixed gradually. Great that we are already seeing tenants getting back to normal business. We do apology inconvenience and are taking corrective actions for the future to avoid these kinds of issues.

[wictorwilen]

(see this as a positive thing - we're actually building SPFx stuff - for realz!)

[vipulkelkar]

Now working in an Australian too..

[koskila]

Just got a confirmation our deployments (mainly European ones) are going through as well :)

[VesaJuvonen]

@wictorwilen - Trust me. We are aware how much SPFx is being used across the world (we track this closely with telemetry) and super happy with the massive growth and adoption curve. Obviously, these kind of issues does not help. Anything can always happen and the key is to learn from them to minimize future possibilities for same issues to occur again.

Appreciate the input from everyone.

[trillian74]

Thanks for getting IT up and running. Our demo is saved, bit a few new gray freight hairs gained

[jonathanhotono]

Still not working in my tenants (Australian servers).. I will try again tomorrow as probably this needs time to propagate.

[freedumz]

I don't know if it's linked
I can install apps but when I try to run them (after their installations) on my PWA, I've a loading page and after that nothing
(I started at 8am and now it's still loading)

[Serhiy-Shekhovtsov]

We can't remove\upgrade any Add-in on SharePoint Online.

[Christian-Stahl]

Now working in an Europe as well, thanks for quick fixing this!.

[VesaJuvonen]

@freedumz and @Serhiy-Shekhovtsov - Would suggest to open up a new issue and provide sufficient amount of details around the issue. How things were installed, what they are and how you tried to use them. Since behavior is different than in this issue, it's better to open a new item, so that your tasks are not getting hidden/buried in comments. Thx.

[submarines-and]

All our apps are also stuck on "We're removing your app"; we started to remove them during the outage listed in this issue.

Is this a separate issue then, or will it be fixed by the same fix that is rolling out for this issue?

[VesaJuvonen]

@submarines-and - it would be helpful to report that as a separate issue, so that your findings are not getting hidden in this one.

Sure - this could be related on this particular issue, but - let’s track that as isolated item and rather reference this issue in details to provide the needed context and insights on what you are currently seeing. Thx.

[pdemro]

All of my tenants are still impacted by the issue. Will continue to test as the day goes on.

[submarines-and]

This is now resolved for us, will also update the other issue

[pdemro]

This looks stable for me today. Thanks guys.

[bmanning31]

FYI, was working this morning. now it's NOT working. same errors as yesterday.

[dougraheem]

Working for me.

[dougraheem]

Thanks Microsoft !

[phoegfeldt]

Europe: I have also had the issue all this week. I managed to get it to work one time yesterday and one time today. But all my other deployment fails. I just tried 30 minutes ago and it still fails.

[phoegfeldt]

I can't see this advisory in my Tenant Admin message center with the SP128660. I can only see MC... messages. If I look in my preferences everything is set to ON.

[phoegfeldt]

This morning it seems to be fine. So let us hope it stays like this.

[bmanning31]

Still not working today. Only working for me 1 out every 10 tries. Same exact error messages, same behaviour as last week. Very frustrating...

[phoegfeldt]

Europe: I am also getting this error again just now. I can't deploy to my developer SharePoint server. I get same error again like last week: Error occurred in deployment step 'Install SharePoint Add-in': The remote server returned an error: (429).

[VesaJuvonen]

Closing this issue for now, since it was a wider issue on the server side, which has been fixed. @phoegfeldt - Can you submit a new issue with additional details. If you are getting 429 exceptions, that refers to throttling and it's a different scenario, That will help us to find the right people internally to track the issue. thx.

Same for @bmanning31 - we would need more details on your exact issue, so would ask to open a new issue with additional details. Thx.

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues