Skip to content

The Angular CLI process did not start listening for requests within the timeout period of 0 seconds #22883

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
vsfeedback opened this issue Jun 12, 2020 · 5 comments
Labels
area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. feature-spa ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Status: Resolved

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


When upgrading our Angular 8 project to Angular 9 this became an issue. Before the upgrade the project was running just fine.

Visual Studio Enterprise 2019 Version 16.5.5 (Windows 10 - 1903)

.NET Core 3.1

Angular 9.1.9

It seems to be an issue that is active for some months now, but all the solutions seems to be a workaround and not an actual fix:

https://github.com/angular/angular-cli/issues/16961

https://stackoverflow.com/questions/55406292/timeoutexception-the-angular-cli-process-did-not-start-listening-for-requests-w

We've tried to edit the package.json and updated "start": "ng serve", to "start": "ng serve --host 0.0.0.0",

This seems to fix the issue if you're using 'Start without Debugging', but when you use 'Start Debugging' it fails again.


Original Comments

Visual Studio Feedback System on 6/9/2020, 03:07 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

(no solutions)

@ghost ghost added the Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. label Jun 12, 2020
@mkArtakMSFT mkArtakMSFT added area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates feature-spa labels Jun 12, 2020
@mkArtakMSFT
Copy link
Contributor

Potentially related to #17277 and #18820

@mkArtakMSFT
Copy link
Contributor

This is a dupe of #18062

@mkArtakMSFT mkArtakMSFT added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Jun 15, 2020
@ghost ghost added the Status: Resolved label Jun 15, 2020
@Knordy
Copy link

Knordy commented Jun 16, 2020

The edit in #17277 ("start": "echo hello && ng serve",) seems to be a valid workaround for now. Will monitor it and reply if it fails again.

We are using UseAngularCliServer and not UseProxyToSpaDevelopmentServer as #18062 is suggesting, but could have potentialy similar underlying issues.

Still hope this gets fixed.

@Knordy
Copy link

Knordy commented Jun 16, 2020

Unfortunately start": "echo hello && ng serve isn't a stable workaround. It still produces the mentioned error.

It show the following message in the debug output window:
Exception thrown: 'System.TimeoutException' in System.Private.CoreLib.dll

@Knordy
Copy link

Knordy commented Jun 19, 2020

So I've tried several things now, as what is indicated in #18820

All fails when using Start Debugging in Visual Studio. So the only possible fix is the suggested fix in the AngularCliMiddleWare as suggested in #18062?

@ghost ghost locked as resolved and limited conversation to collaborators Jul 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. feature-spa ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Status: Resolved
Projects
None yet
Development

No branches or pull requests

3 participants