Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ListView Command Set extension not loading on a specific list #10074

Open
2 of 9 tasks
vladigubler opened this issue Jan 10, 2025 · 14 comments
Open
2 of 9 tasks

ListView Command Set extension not loading on a specific list #10074

vladigubler opened this issue Jan 10, 2025 · 14 comments
Labels
type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.

Comments

@vladigubler
Copy link

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

Additional environment details

  • browser version : latest Edge and Chrome (but not Firefox)
  • SPFx version: 1.15
  • Node.js version: 14.21.3
  • New Lists interface

Describe the bug / error

On one specific Custom list only the SPFx extensions do not load. Works well on other lists and, strangely, works in Firefox.
When it doesn't work, the following lines are found in Console for each one of the extensions:

"A preload for 'https://storage.infowisesolutions.com/ufspfx/v1400/infowise-design.js' is found, but is not used due to an unknown reason."

Steps to reproduce

Not sure how to reproduce, but it consistently doesn't load on a particular list, but works on all the other lists within the same site, with or without the new Lists interface. This is a simple SPFx list extensions that adds some buttons to the toolbar.

This is the error:
errspfx

Expected behavior

Loads on all lists in the site.

@vladigubler vladigubler added the type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. label Jan 10, 2025
@Kolyangus
Copy link

I would just add that we have also been experiencing similar issues with this meaning that customers are unable to perform functionality.

I did see a closed issue with relation to embedded pages for Command Set #10057 as this is a fairly new issue that has been closed and whether this had an impact causing the above?

@vladigubler
Copy link
Author

As far as I can see, it affects certain lists, but not others. I can't see any difference between the lists, same template, same everything. It is persistent though. The affected lists stay affected, no matter what I do.
The only (imperfect) workaround is to add a custom column to the view, which forces the regular, not MS Lists, interface.

@reedpamsft
Copy link
Contributor

reedpamsft commented Jan 13, 2025

Thanks folks! We have a fix for the issue, and just need to evaluate our options for rolling it out. Workaround would be to visit the list/library in "full" mode (ie: not in a web part).

@vladigubler
Copy link
Author

We are visiting it in full mode, we don't use web parts for this. It is an extremely wide-spread issue and I feel it's growing every day, probably as more tenants get the newest UI.

@vladigubler
Copy link
Author

Note, I also get this sometimes: A preload for 'https://storage.infowisesolutions.com/ufspfx/v1400/infowise-slp.js' is found, but is not used because the request credentials mode does not match. Consider taking a look at crossorigin attribute. I have no idea where it's coming from and why it would suddenly ask for this attribute. It's something on your side.

@vladigubler
Copy link
Author

And there is also this now: The resource at “https://storage.infowisesolutions.com/ufspfx/v1400/infowise-design.js” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly.
This happens in Firefox.

@vladigubler
Copy link
Author

Also, today the issue spread to all lists using the MS Lists interface, please help!

@reedpamsft
Copy link
Contributor

reedpamsft commented Jan 14, 2025

And there is also this now: The resource at “https://storage.infowisesolutions.com/ufspfx/v1400/infowise-design.js” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. This happens in Firefox.

@vladigubler that seems unrelated; please feel free to open a new thread about those.

@vladigubler
Copy link
Author

@reedpamsft What do you mean unrelated? these are all related to the SPFx customizer not being loaded. It refuses to loads the JS file, the messages change according to the type of browser. In Edge/Chrome the usual message is usually "is found, but is not used because the request credentials mode does not match. Consider taking a look at crossorigin attribute" or " is found, but is not used due to an unknown reason"

@reedpamsft
Copy link
Contributor

@vladigubler okay, I'm really sorry, I'm getting this mixed up with another issue that came across my inbox... I'll send this to the appropriate folks.

@vladigubler
Copy link
Author

@reedpamsft Is there any ETA when it's going to be fixed. According to our customers it stopped working within the last 24 hours on all the lists it previously worked on. I'm guessing an update was recently pushed out?

@natalieethell
Copy link

@vladigubler as discussed over mail, I believe this issue should be fixed now. We rolled back a change that caused a regression for this experience.

@Kolyangus
Copy link

I wasn't added to the mail correspondence but confirm from my side the issue appears to be resolved based on the roll back. Hopefully it's also solved for @vladigubler

@vladigubler
Copy link
Author

vladigubler commented Jan 16, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Projects
None yet
Development

No branches or pull requests

4 participants