Skip to content

Pop up won't go away when using 1.21.1 even though gulp serve is running and everything is working fine: "Your web part will not appear in the toolbox. Please make sure "gulp serve" is running in a web part project." #10245

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

Closed
1 of 9 tasks
kbeeveer46 opened this issue May 8, 2025 · 11 comments
Assignees
Labels
sharepoint-developer-support sharepoint-developer-support type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.

Comments

@kbeeveer46
Copy link

kbeeveer46 commented May 8, 2025

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

Node v22.15.0
SPFx v1.21.1

Describe the bug / error

I upgraded to 1.21.1 and everything is working fine. I can build and run my project and all web parts seem to be working fine but this pop up appears on every page load. This also happens when creating a new blank SPFx project from scratch. I just tested it by editing the default web part and refreshing the page.

I'm using the following workbench URL

https://xxxxxx.sharepoint.com/sites/ClientPortalQA/_layouts/15/workbench.aspx?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/build/manifests.js

and when I browse to the manifest file it loads and I can view it

https://localhost:4321/temp/build/manifests.js

Image

The console shows the following error in my custom project (not a new one). Why is it showing the old path in the first few lines but correct path in the last 4?

Failed to load debug manifests: Error: Script error for "https://localhost:4321/temp/manifests.js"
https://requirejs.org/docs/errors.html#scripterror

Uncaught Error Error: Script error for "http://localhost:4321/temp/manifests.js"
https://requirejs.org/docs/errors.html#scripterror
    at makeError (<eval>/VM46947589:5:1843)
    at onScriptError (<eval>/VM46947589:5:17037)
    --- script ---
    at req.createNode (<eval>/VM46947589:5:3139)
    at req.load (<eval>/VM46947589:5:3316)
    at load (<eval>/VM46947589:5:16641)
    at load (<eval>/VM46947589:5:10104)
    at fetch (<eval>/VM46947589:5:9905)
    at check (<eval>/VM46947589:5:11164)
    at enable (<eval>/VM46947589:5:13227)
    at enable (<eval>/VM46947589:5:15757)
    at eval (<eval>/VM46947589:5:13084)
    at eval (<eval>/VM46947589:5:1602)
    at each (<eval>/VM46947589:5:1062)
    at enable (<eval>/VM46947589:5:12586)
    at init (<eval>/VM46947589:5:9623)
    at eval (<eval>/VM46947589:5:15076)
    --- setTimeout ---
    at req.nextTick (<eval>/VM46947589:5:2480)
    at s (<eval>/VM46947589:5:15015)
    at requirejs (<eval>/VM46947589:5:2381)
    at <anonymous> (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:15858)
    at e._require (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:15830)
    at <anonymous> (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:12297)
    at e.load (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:12222)
    at e.loadScript (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:12129)
    at e.loadScript (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:3264)
    at I (res-1.cdn.office.net/files/sp-client/chunk.sp-loader-debug-handlers_en-us_9e32893ac186dcb873d1.js:1:4013)
    at <anonymous> (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:3557)
    --- Promise.then ---
    at e._loadDebugManifestsForWorkbench (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:3495)
    at e._loadDebugManifestsForWorkbench (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:200:1190)
    at <anonymous> (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:270:36898)
    --- Promise.catch ---
    at onLoad (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:270:36874)
    at n._load (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:266:71069)
    at e._initializeApplication (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:266:68637)
    at e._initializeApplicationWithTelemetry (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:266:66769)
    at e.startApplication (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:266:66176)
    at e.navigate (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:266:54569)
    at t.navigateToApplication (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:266:62012)
    at c (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:209:697)
    at <anonymous> (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:209:515)
    at s (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:209:113)
    at e._startApplication (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:3624)
    at e._startApplication (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:200:186)
    at <anonymous> (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:25685)
    --- Promise.then ---
    at e.start (res-1.cdn.office.net/files/sp-client/sp-webpart-workbench-assembly_en-us_3d1672af64bc201f3282d671ff21612d.js:202:23550)
    at loaderStart (xxxxxx.sharepoint.com/sites/ClientPortalQA/_layouts/15/workbench.aspx?debug=true&noredir=true&debugManifestsFile=https%3A%2F%2Flocalhost%3A4321%2Ftemp%2Fbuild%2Fmanifests.js꞉50:210:59:74)
    at startSpfx (xxxxx.sharepoint.com/sites/ClientPortalQA/_layouts/15/workbench.aspx?debug=true&noredir=true&debugManifestsFile=https%3A%2F%2Flocalhost%3A4321%2Ftemp%2Fbuild%2Fmanifests.js꞉50:210:71:29)
    at <anonymous> (xxxxxx.sharepoint.com/sites/ClientPortalQA/_layouts/15/workbench.aspx?debug=true&noredir=true&debugManifestsFile=https%3A%2F%2Flocalhost%3A4321%2Ftemp%2Fbuild%2Fmanifests.js꞉50:210:98:21)
    at <anonymous> (xxxxx.sharepoint.com/sites/ClientPortalQA/_layouts/15/workbench.aspx?debug=true&noredir=true&debugManifestsFile=https%3A%2F%2Flocalhost%3A4321%2Ftemp%2Fbuild%2Fmanifests.js꞉50:210:102:15)

This is the terminal log after I ran gulp serve on my custom project (not a new one) and added a web part

PS C:\RespositoriesGit\CP\clientportalsharepoint> gulp serve
Build target: DEBUG
[09:11:15] Using gulpfile C:\RespositoriesGit\CP\clientportalsharepoint\gulpfile.js
[09:11:15] Starting 'serve'...
[09:11:15] Starting gulp
[09:11:15] Starting subtask 'spfx-serve'...
[09:11:15] [spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/build/manifests.js
[09:11:16] Starting server...
[09:11:16] Finished subtask 'spfx-serve' after 1.38 s
[09:11:16] Starting subtask 'pre-copy'...
[09:11:16] Finished subtask 'pre-copy' after 30 ms
[09:11:16] Starting subtask 'copy-static-assets'...
[09:11:16] Starting subtask 'sass'...
[09:11:16] Server started https://localhost:4321
[09:11:16] LiveReload started on port 35729
[09:11:16] Running server
Opening https://xxxxxx.sharepoint.com/sites/ClientPortalQA/_layouts/15/workbench.aspx?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/build/manifests.js using the default OS app
[09:11:18] Finished subtask 'sass' after 1.72 s
[09:11:18] Starting subtask 'lint'...
[09:11:18] [lint] eslint version: 8.57.1
[09:11:18] Starting subtask 'tsc'...
[09:11:18] [tsc] typescript version: 5.3.3
  Request: '/ws'
[09:11:25] Finished subtask 'copy-static-assets' after 8.55 s
[09:11:33] Finished subtask 'lint' after 15 s
  Request: '/ws'
[09:11:42] Finished subtask 'tsc' after 24 s
[09:11:42] Starting subtask 'post-copy'...
[09:11:42] Finished subtask 'post-copy' after 206 μs
[09:11:42] Starting subtask 'configure-webpack'...
[09:11:43] Applying QA settings to webpack
[09:11:43] Finished subtask 'configure-webpack' after 582 ms
[09:11:43] Starting subtask 'webpack'...
[09:12:11] Finished subtask 'webpack' after 28 s
[09:12:11] Starting subtask 'reload'...
[09:12:11] Finished subtask 'reload' after 7.73 ms
  Request: '/ws'
  Request: '/temp/build/manifests.js'
  Request: '/temp/build/manifests.js'
  Request: '/temp/manifests.js'
  Request: '/temp/manifests.js'
  Request: '/dist/tt-audit-tracker-web-part.js'
  Request: '/dist/tt-audit-tracker-web-part.js'
  Request: '/dist/primeicons_062070972fbad0f4fbb3.woff'
  Request: '/dist/proxima_nova_black_a8d4dae6defc9aaa715e.woff'
  Request: '/dist/proxima_nova_bold_0749b30b4128ba2c6b3c.woff'
  Request: '/dist/proxima_nova_regular_231e91b70df7fecb5b1d.woff'
  Request: '/dist/primeicons_062070972fbad0f4fbb3.woff'
  Request: '/dist/proxima_nova_black_a8d4dae6defc9aaa715e.woff'
  Request: '/dist/proxima_nova_bold_0749b30b4128ba2c6b3c.woff'
  Request: '/dist/proxima_nova_regular_231e91b70df7fecb5b1d.woff'
  Request: '/dist/chunk.USAndCanadaGeoJSON.js'
  Request: '/dist/chunk.USAndCanadaGeoJSON.js'

Steps to reproduce

Create a new project and run it. The pop up will appear when the browser automatically opens by VS Code and after making an edit to the default web part and refreshing the page.

Expected behavior

The pop up should not appear because Gulp Serve is already running

@kbeeveer46 kbeeveer46 added the type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. label May 8, 2025
@Ashlesha-MSFT
Copy link

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

@Ashlesha-MSFT Ashlesha-MSFT self-assigned this May 8, 2025
@Ashlesha-MSFT Ashlesha-MSFT added the sharepoint-developer-support sharepoint-developer-support label May 8, 2025
@Ashlesha-MSFT
Copy link

Ashlesha-MSFT commented May 9, 2025

@kbeeveer46,
This issue has already been identified and reported, and engineering team has provided a fix. #10053 (comment)

https://learn.microsoft.com/en-us/sharepoint/dev/spfx/release-1.21.1

Image

@Ashlesha-MSFT Ashlesha-MSFT added the status:rolling in production The fix has been created and it's currently rolling across all production tenants label May 9, 2025
@kbeeveer46
Copy link
Author

kbeeveer46 commented May 9, 2025

I am already on v1.21.1. The issue only appears after upgrading to it. Someone also left a comment in that post that the issue still appears in 1.21.1. The engineering team has not replied with a fix. Here's a screen recording I took after creating a new 1.21.1 project and running it. https://streamable.com/2ynz5g

@Ashlesha-MSFT
Copy link

I am already on v1.21.1. The issue only appears after upgrading to it. Someone also left a comment in that post that the issue still appears in 1.21.1. The engineering team has not replied with a fix. Here's a screen recording I took after creating a new 1.21.1 project and running it. https://streamable.com/2ynz5g

We’ll follow up with our engineering team and provide you with the latest status.

@pravin-durgam
Copy link

pravin-durgam commented May 11, 2025

I am already on v1.21.1. The issue only appears after upgrading to it. Someone also left a comment in that post that the issue still appears in 1.21.1. The engineering team has not replied with a fix. Here's a screen recording I took after creating a new 1.21.1 project and running it. https://streamable.com/2ynz5g

We’ll follow up with our engineering team and provide you with the latest status.

This is a huge blocker for testing the SPFx web part changes, could you please update on the same?

@Ashlesha-MSFT Ashlesha-MSFT removed the status:rolling in production The fix has been created and it's currently rolling across all production tenants label May 12, 2025
@s-KaiNet
Copy link
Contributor

@pravin-durgam you can use a regular SPFx page for testing (not work bench), on a normal page there are no any issues. You just need to add a query string to the end of the page ?debug=true&noredir=true&debugManifestsFile=https%3A%2F%2Flocalhost%3A4321%2Ftemp%2Fbuild%2Fmanifests.js.
If you still need work bench, you can use any plugin, which runs JavaScript on a page and add below JS (this is the script for a popular TamperMonkey addin):

// ==UserScript==
// @name         New Userscript
// @namespace    http://tampermonkey.net/
// @version      2025-05-12
// @description  try to take over the world!
// @author       You
// @match        https://<your tenant>.sharepoint.com/*
// @icon         https://www.google.com/s2/favicons?sz=64&domain=sharepoint.com
// @grant        none
// ==/UserScript==

(function() {
    'use strict';

    const url = window.location.href;
    if(url.indexOf("_layouts/15/workbench.aspx") == -1) return;

    const interval = setInterval(function(){
        if(document.querySelector("[data-automation-id=GulpServeWarningOkButton]")){
            document.querySelector("[data-automation-id=GulpServeWarningOkButton]").click();
            clearInterval(interval);
        }
    }, 50);
})();

If you want to use it, you need to replace <your tenant> with real tenant url.

@kbeeveer46
Copy link
Author

This issue appears to be fixed now. I assume it was a change on Microsoft's end?

@Ashlesha-MSFT
Copy link

@kbeeveer46,
I can also confirm the fix for my tenant.
If fix is confirmed, can we move aheaad and close the issue?

@pravin-durgam
Copy link

@kbeeveer46, I can also confirm the fix for my tenant. If fix is confirmed, can we move aheaad and close the issue?

The issue seems to be fixed, It's working great. Thank you Microsoft team for the immediate fix.

@pravin-durgam you can use a regular SPFx page for testing (not work bench), on a normal page there are no any issues. You just need to add a query string to the end of the page ?debug=true&noredir=true&debugManifestsFile=https%3A%2F%2Flocalhost%3A4321%2Ftemp%2Fbuild%2Fmanifests.js. If you still need work bench, you can use any plugin, which runs JavaScript on a page and add below JS (this is the script for a popular TamperMonkey addin):

// ==UserScript==
// @name New Userscript
// @namespace http://tampermonkey.net/
// @Version 2025-05-12
// @description try to take over the world!
// @author You
// @match https://.sharepoint.com/*
// @ICON https://www.google.com/s2/favicons?sz=64&domain=sharepoint.com
// @grant none
// ==/UserScript==

(function() {
'use strict';

const url = window.location.href;
if(url.indexOf("_layouts/15/workbench.aspx") == -1) return;

const interval = setInterval(function(){
    if(document.querySelector("[data-automation-id=GulpServeWarningOkButton]")){
        document.querySelector("[data-automation-id=GulpServeWarningOkButton]").click();
        clearInterval(interval);
    }
}, 50);

})();
If you want to use it, you need to replace <your tenant> with real tenant url.

This is great workaround, However the fix has been applied by Microsoft now, I can confirm the same today. Thank you for your great help.

@pravin-durgam
Copy link

@kbeeveer46, I can also confirm the fix for my tenant. If fix is confirmed, can we move aheaad and close the issue?

The issue seems to be fixed today, It's working great, Thank you Microsoft team for the immediate fix.

@Ashlesha-MSFT
Copy link

@kbeeveer46,
Please help us by closing the issue and filling up below feedback form
https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4mTPG34N0xHuJATbbeqmGlUMTJVMzY0TlAwNThWWlVCNFY4MExFNjNTUC4u

Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sharepoint-developer-support sharepoint-developer-support 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