Sp-dev-docs: CommandSet extensions stopped working

Created on 29 Mar 2019 · 45Comments · Source: SharePoint/sp-dev-docs

Observed Behavior

A CommandSet extension which was working fine a couple of days ago stopped working yesterday.
The console logs:
Uncaught Error: There is no operation handler registered for '{"operation_3":["getItems_1","spField_296"]}'.
Error source: https://spoprod-a.akamaihd.net/files/odsp-next-prod_2019-03-15-sts_20190326.002/splistitemsscope-is-mini-8f54d6ff.js

I've tried it on 3 different tenants, all throwing this error.

Steps to Reproduce

Even a newly generated extension throws this error en doesn't do anything. A console.log() in the onInit method doesn't even appear in the console.

spfx-general fixed bug-suspected

Source

RoelVB

Most helpful comment

We are currently actively investigating this.

VesaJuvonen on 4 Apr 2019

👍3

All 45 comments

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

msft-github-bot on 29 Mar 2019

I have the same error since this morning.

PooLP on 29 Mar 2019

It looks like the problem got resolved. For me the extension started working again.

RoelVB on 29 Mar 2019

Correction. Looks like extension in debug mode are still not working.

RoelVB on 29 Mar 2019

and I also have the problem on the commandSet

PooLP on 29 Mar 2019

Same problem here. Started about one hour ago.
CommandSets suddenly show up on the wrong list or are output twice. Clicking on them does not execute them. Browser console shows the above mentioned error.

cwdata on 29 Mar 2019

Are your tenants on First (targeted) Release?

PiotrekKrakowiak on 29 Mar 2019

Mine is on targeted release.

cwdata on 29 Mar 2019

👍1

I can only repro on TR(FR) - no repro on standard release. Anybody with a Repro on SR? :-)

PiotrekKrakowiak on 29 Mar 2019

Same here. Problem only exists on targeted release!

RoelVB on 29 Mar 2019

👍1

The PG is rolling back a feature they deployed recently, they said it should be rolled back in about 20 min. If it was the cause, the issue should disappear when it rolls back.

westleyMS on 29 Mar 2019

👍1

Still nearly the same error at 19:12 (Utc +1)
The only thing that changed: The CommandSet now executes when clicking on the link. But it is still shown twice, has no Icon and the error in the console is also still there.

cwdata on 29 Mar 2019

did you clear the browser cache? ctrl+F5?

westleyMS on 29 Mar 2019

Yes I even cleared it through the browser settings. Still not working.

cwdata on 29 Mar 2019

Please use the F12 tools to see the sp-client-prod or odsp-next-prod file versions. Just get the full file names and post them here.

westleyMS on 29 Mar 2019

it still does not work this morning, cache is completely cleared.

@westleyMS : on site collection I have only odsp-next-prod files directory name :
ex : https://spoprod-a.akamaihd.net/files/odsp-next-prod_2019-03-15-sts_20190328.001/require-a19851d1.js

PooLP on 30 Mar 2019

Deployed extensions seems to work fine now, but debug mode still doesn't work.

Something strange happen when appending only ?loadSPFX=true to the URL. A button get added to the commandbar, this button has the name of the (deployed) extension, but does nothing when clicking it. And of course I don't have a button like this defined in the extension.

When I do use a full debug query/url the same issue appears and the locally running extension doesn't load.

RoelVB on 2 Apr 2019

For us it worked yesterday, but today the error is back like it was on Friday.
The file name changed slightly:
https://spoprod-a.akamaihd.net/files/odsp-next-prod_2019-03-15-sts_20190330.001/splistitemsscope-is-mini-a9a8d6f1.js

cwdata on 2 Apr 2019

Yes, I can confirm extensions have stopped working :-)
Spent whole morning trying to figure out what went wrong.
Thanks for raising the issue otherwise i would have spent the whole day..haha

harshdamaniahd on 2 Apr 2019

Stopped working for me when using gulp serve (Works OK for deployed version) on a Target Release tenant

https://spoprod-a.akamaihd.net/files/odsp-next-prod_2019-03-15-sts_20190330.001/splistitemsscope-is-mini-a9a8d6f1.js

Uncaught Error: There is no operation handler registered for '{"operation_3":["getItems_1","spField_296"]}'.
at e.r (splistitemsscope-is-mini-a9a8d6f1.js:1)
at new e (splistitemsscope-is-mini-a9a8d6f1.js:1)
at splistitemsscope-is-mini-a9a8d6f1.js:1
at splistitemsscope-is-mini-a9a8d6f1.js:1
at splistitemsscope-is-mini-a9a8d6f1.js:1
at splistitemsscope-is-mini-a9a8d6f1.js:1
at dispatch (splistitemsscope-is-mini-a9a8d6f1.js:1)
at Object. (splistitemsscope-is-mini-a9a8d6f1.js:1)
at listviewdataprefetch-mini-97237397.js:15
at Object.next (listviewdataprefetch-mini-97237397.js:15)

statto1974 on 2 Apr 2019

👍1

For me base64 image stopped working , can anyone confirm this ?

harshdamaniahd on 2 Apr 2019

Yes, I can confirm extensions have stopped working :-)
Spent whole morning trying to figure out what went wrong.
Thanks for raising the issue otherwise i would have spent the whole day..haha

I also have this issue on one of my tenants, is it something i should do to get it fixed?

kwilsson on 2 Apr 2019

@kwilsson I guess something is wrong in targeted release.I will suggest dont spend time for now.Lets wait.
Many users are facing this issue.

harshdamaniahd on 2 Apr 2019

same issue here with base64 image. Extension is sort of working fine but images are not appearing...

majidali on 3 Apr 2019

I got the same error here. On targeted release. My command extension does not work at all. Reverting to standard release for now.

spdavid on 4 Apr 2019

Same error here; targeted release. Both when using gulp serve and deployed version.

Stopped working for me when using gulp serve (Works OK for deployed version) on a Target Release tenant

Louren on 4 Apr 2019

The same problems for us. I also noticed that this issue appears randomly, but much more often column extensions and view commands do not load correctly than loads as expected, when refreshing page several times in a row.

JovitaLipkiene on 4 Apr 2019

I have this issue too. Sorry if there is an obvious answer to this question but what exactly do you mean by "targeted release"?

JJungbluth on 4 Apr 2019

@andrewconnell @VesaJuvonen you have any news for this bug, it becomes very blocker. Thanks.

PooLP on 4 Apr 2019

I have this issue too. Sorry if there is an obvious answer to this question but what exactly do you mean by "targeted release"?

in Office 365 admin under organization profile you can set your Release Preferences to be targeted release which means you get early updates.

spdavid on 4 Apr 2019

👍1

@JJungbluth said:

... what exactly do you mean by "targeted release"?
https://docs.microsoft.com/en-us/office365/admin/manage/release-options-in-office-365?view=o365-worldwide

andrewconnell on 4 Apr 2019

👍2

We are currently actively investigating this.

VesaJuvonen on 4 Apr 2019

👍3

Same problem here!

Hope you guys can figure it out

EdwKro on 4 Apr 2019

This issue is actively being worked on. Hopefully will get sorted out soon.

VesaJuvonen on 4 Apr 2019

👍1

Fix has been now applied and situation should be reverted to normal. This was an unfortunate regression which got passed the testing. Please confirm the situation from our side as well, but based on the tenants we use for validation, we cannot anymore see this one. Thanks for confirmation advance.

VesaJuvonen on 4 Apr 2019

👍1

It seems the issue with the Command Set Extensions is gone in my tenant but I also lost all new library features that I received around the same time that I started noticing the issue. These include Bulk Check-out/in, Signals, the Shimmer background and the new status indicator when uploading/checking out etc files.

patrikhellgren on 4 Apr 2019

In our tenant extensions are also back to normal operation.

cwdata on 5 Apr 2019

Everything is back to normal :-)

image not showing up in extension - fixed
Not working in debug mode or when gulp serve - fixed ("Execute function not executing") - fixed

harshdamaniahd on 5 Apr 2019

I also confirming that issues gone.

JovitaLipkiene on 5 Apr 2019

Thx everyone for confirming the status. Sorry for the inconvenience. Planned features which might have been there for a while, will come back after the regression has been fixed.

VesaJuvonen on 8 Apr 2019

We were affected by this issue when it first occurred. The fix worked as the error message went away and our SPFX command bar extension started working again.

I noticed this morning that it has come back on one of our tenants. I get the below error when I select an item in the site pages library and click the delete button in the command bar:

splistitemsscope-is-mini-dc133da0.js:1 Uncaught Error: There is no operation handler registered for '{"operation_3":["getItems_1","progress-deleteItems_509"]}'. at e.n (spofiles-mini-6714dbfb.js:1) at new e (splistitemsscope-is-mini-dc133da0.js:1) at splistitemsscope-is-mini-dc133da0.js:1 at splistitemsscope-is-mini-dc133da0.js:1 at splistitemsscope-is-mini-dc133da0.js:1 at splistitemsscope-is-mini-dc133da0.js:1 at dispatch (splistitemsscope-is-mini-dc133da0.js:1) at Object.<anonymous> (splistitemsscope-is-mini-dc133da0.js:1) at listviewdataprefetch-mini-bfd20981.js:15 at Object.next (listviewdataprefetch-mini-bfd20981.js:15)

Also I'm noticing that our SPFX add-in is not loading in this tenant (using gulp serve) but it is in others.

csgkeith on 17 Apr 2019

@VesaJuvonen @andrewconnell

Not getting the error anymore, but gulp serve isn't working. My Command Set isn't being loaded into the library I have set up in serve.json

Have cleared history and cache

Have set up a series of Console logs and it does not even initiate the command set.

Not sure if it's relevant, but these are the only error messages showing in the console.

Refused to get unsafe header "SPClientServiceRequestDuration"
Refused to get unsafe header "SPRequestGuid"
Refused to get unsafe header "SPRequestGuid"
Refused to get unsafe header "X-SERVICEWORKER-DATA-SOURCE"

If I package and deploy through the app catalog it works correctly.

statto1974 on 17 Apr 2019

👍2

The issue has started appearing again, @VesaJuvonen can you please validate if there were any update done on the List Field customizer.

Please see the error below:
Uncaught Error: There is no operation handler registered for '{"operation_4":["getItems_16","spColumnAdapter_222"]}'.
at e.n (spofiles-mini-be65a0bf.js:1)
at new e (splistitemsscope-is-mini-8ce35f12.js:1)
at splistitemsscope-is-mini-8ce35f12.js:1
at splistitemsscope-is-mini-8ce35f12.js:1
at splistitemsscope-is-mini-8ce35f12.js:1
at splistitemsscope-is-mini-8ce35f12.js:1
at dispatch (splistitemsscope-is-mini-8ce35f12.js:1)
at Object. (splistitemsscope-is-mini-8ce35f12.js:1)
at listviewdataprefetch-mini-f46dba5c.js:15
at Object.next (listviewdataprefetch-mini-f46dba5c.js:15)

gagan2singh on 30 Jun 2019

Hi @gagan2singh,
this is a closed issue. If you want somebody to help you then it's recommended to open a new issue.
You can refer to this one if you think it is related.

cwdata on 1 Jul 2019

👍1

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

msft-github-bot on 24 Jan 2020

Was this page helpful?

0 / 5 - 0 ratings