Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Could not load settings for 'ca_sln.WebUI'

See original GitHub issue

Describe the bug When loading the main page of the client application in Chrome, the following error occurs once in the browser console. The application is being run from Windows 10 Pro x64.

core.js:7187 ERROR Error: Uncaught (in promise): Error: Could not load settings for 'ca_sln.WebUI'
Error: Could not load settings for 'ca_sln.WebUI'
    at AuthorizeService.<anonymous> (authorize.service.ts:179)
    at Generator.next (<anonymous>)
    at fulfilled (authorize.interceptor.ts:10)
    at ZoneDelegate.invoke (zone-evergreen.js:359)
    at Object.onInvoke (core.js:30892)
    at ZoneDelegate.invoke (zone-evergreen.js:358)
    at Zone.run (zone-evergreen.js:124)
    at zone-evergreen.js:855
    at ZoneDelegate.invokeTask (zone-evergreen.js:391)
    at Object.onInvokeTask (core.js:30873)
    at ZoneDelegate.invokeTask (zone-evergreen.js:390)
    at Zone.runTask (zone-evergreen.js:168)
    at drainMicroTaskQueue (zone-evergreen.js:559)
    at resolvePromise (zone-evergreen.js:797)
    at zone-evergreen.js:707
    at fulfilled (authorize.interceptor.ts:10)
    at ZoneDelegate.invoke (zone-evergreen.js:359)
    at Object.onInvoke (core.js:30892)
    at ZoneDelegate.invoke (zone-evergreen.js:358)
    at Zone.run (zone-evergreen.js:124)
    at zone-evergreen.js:855
    at ZoneDelegate.invokeTask (zone-evergreen.js:391)
    at Object.onInvokeTask (core.js:30873)
    at ZoneDelegate.invokeTask (zone-evergreen.js:390)
    at Zone.runTask (zone-evergreen.js:168)
    at drainMicroTaskQueue (zone-evergreen.js:559)

The following error occurs twice:

ERROR Error: Could not load settings for 'ca_sln.WebUI'
    at AuthorizeService.<anonymous> (authorize.service.ts:179)
    at Generator.next (<anonymous>)
    at fulfilled (authorize.interceptor.ts:10)
    at ZoneDelegate.invoke (zone-evergreen.js:359)
    at Object.onInvoke (core.js:30892)
    at ZoneDelegate.invoke (zone-evergreen.js:358)
    at Zone.run (zone-evergreen.js:124)
    at zone-evergreen.js:855
    at ZoneDelegate.invokeTask (zone-evergreen.js:391)
    at Object.onInvokeTask (core.js:30873)
    at ZoneDelegate.invokeTask (zone-evergreen.js:390)
    at Zone.runTask (zone-evergreen.js:168)
    at drainMicroTaskQueue (zone-evergreen.js:559)

To Reproduce Steps to reproduce the behavior:

Create a new project from the template per the directions in the readme.
Use dotnet run to initialize project
Load index in Chrome

Expected behavior The page should not launch with errors.

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

jasontaylordevcommented, Feb 14, 2021

First, run npm start within WebUI/ClientApp. Then, run dotnet run from within WebUI. You can then access the site at **https://localhost:5001/. More details here; https://github.com/jasontaylordev/CleanArchitecture/blob/main/README.md.

1reaction

tparikkacommented, Dec 9, 2019

That worked! One of the last build messages written to the console is:

info: Microsoft.AspNetCore.SpaServices[0]
      ** Angular Live Development Server is listening on localhost:52280, open your browser on http://localhost:52280/ **

So that was the host I connected to. Admittedly I’m still really new to web app development but it might be helpful to add something mentioning the connect port to the readme?