Skip to content

Webpart is not beeing hosted #10217

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

Open
1 of 9 tasks
ZzyzxIsAlreadyTaken opened this issue Apr 30, 2025 · 3 comments
Open
1 of 9 tasks

Webpart is not beeing hosted #10217

ZzyzxIsAlreadyTaken opened this issue Apr 30, 2025 · 3 comments
Assignees
Labels
area:spfx Category: SharePoint Framework (not extensions related) status:rolling in production The fix has been created and it's currently rolling across all production tenants type:bug-confirmed Confirmed bug, not working as designed / expected.

Comments

@ZzyzxIsAlreadyTaken
Copy link

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

None

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
  • Version 135.0.3179.98 (Official build) (arm64)
  • SPFx version
  • 1.21
  • Node.js version
  • 22.15.0
  • etc

Describe the bug / error

The web part is not built properly, or there is some referencing errors to manifests file.

If I manually copy the manifest file to the old location it will run so in one project I built a gulp task to copy it each time. But I will always get that warning message box that the web part will not appear in the toolbox.

Image

Steps to reproduce

  1. create a web part project
  2. try to run it in hosted workbench
  3. get no results

Expected behavior

no issues when running gulp serve --nobrowser

@ZzyzxIsAlreadyTaken ZzyzxIsAlreadyTaken added the type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. label Apr 30, 2025
@jvanpiccs
Copy link

Hi, in my case the webpart its shown in the toolbox.

There is a previous similar issue here
#10053

Appears to be a problem between the workbench and this change with the manifests files locations. The workbench appears to be looking for the 2 locations, even if the location its found, the alert pop ups.

I'm downgrading to spfx 1.20 until the bug is fixed.

@Amey-MSFT Amey-MSFT self-assigned this May 2, 2025
@Amey-MSFT
Copy link

Hello @ZzyzxIsAlreadyTaken,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

@VesaJuvonen
Copy link
Contributor

thx @jvanpiccs on providing great response for @ZzyzxIsAlreadyTaken. As noted - web part is there and this is a false message, but it's for sure confusing. This will be addressed with server side update, which starts rolling out to production gradually today and next week. Will be fixed automatically without client side updates.

@VesaJuvonen VesaJuvonen added area:spfx Category: SharePoint Framework (not extensions related) type:bug-confirmed Confirmed bug, not working as designed / expected. status:rolling in production The fix has been created and it's currently rolling across all production tenants and removed type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. labels May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:spfx Category: SharePoint Framework (not extensions related) status:rolling in production The fix has been created and it's currently rolling across all production tenants type:bug-confirmed Confirmed bug, not working as designed / expected.
Projects
None yet
Development

No branches or pull requests

4 participants