schemastore | A collection of JSON schema files including full API | REST library

Pls share your docker run command. I am sure you specified -p option.

I am guessing it looks like below:

docker run -p 57000:8080

8080 will be used from within docker container network.

From host machine you'll have access to the API using with 57000.

I would really like to think that the name of the first jsx_runtime would be jsx_runtime_0 and maybe even that if there was only one jsx_runtime then it wasn't suffixed at all by a bundler!

That's no proof, but it made me speculate whether you've actually got two versions of React coming in because each of two modules you include in your project declare it as a dependency (not a peer dependency) and therefore have their own copies which they reference in the bundle.

Since each copy of React uses a different closure to store top-level stuff, this means it notices if e.g. useState is called in the context of a different copy of React.

I figured it out. Instead of

Following settings have worked kesterl launchsetting (for environment variable name reference)

It looks like port 8080 is mapped to port 443

port 433 is https so make sure you should are using https://localhost:8080 or https://127.0.0.1:8080

I finally solved the issue of why the API was returning a 500 error whenever a request was sent to it.

Upon checking the logs in the 'stdout' file using Kudu I spotted the following error:

So strange and we did not face such issue before. Try something like these:

1) disable any third party extensions under Extensions--> Manage Extensions-->Installed to check if there is an extension caused that.

2) try to reset vs settings under Tools->Import and Export Settings-->Reset vs settings, and you can also make a backup of your settings.

3) close VS, delete .vs hidden folder under the solution folder, bin and obj folder, then restart VS to test again.

4) use devenv /safemode under Developer Command Prompt for VS to start a pure VS to test it.

5) create a new project to test whether the issue happens again.

6) repair vs or update it if there is a new release version.

Besides, if those do not help, you should describe your issue in detail to share a small sample with us to help us troubleshoot it.

You're confusing your OS's environment variables with the .NET Core runtime environment. They've got the same name, and one can get promoted to the other, but they're not the same.

The environment variables in launchSettings.json ("runtime environment" or "host configuration values") do not get promoted to actual environment variables of the OS, the latter which you can read through Environment.GetEnvironmentVariable().

You can read the application's ASPNETCORE_ENVIRONMENT through IHostingEnvironment.Environment or IWebHostEnvironment.EnvironmentName.

To recap: you should not use Environment.GetEnvironmentVariable() to read the ASPNETCORE_ENVIRONMENT from the OS's environment variables, because the .NET Core environment can be set in different ways.

It's the other way around: during the host initialization, the ASPNETCORE_ENVIRONMENT environment variable is read from the operating system, but this value can be provided in different ways, namely through the launchSettings.json, .vscode/launch.json or one can even use AddCommandLine(args), and then:

Simulators ip is different from your host machine's ip. Although they are in the same LAN. You can change the ip in this url.