Publish to Azure WebApp succeeds, but SPA never starts #558

Closed
opened 2025-08-09 17:16:45 +00:00 by fergalmoran · 0 comments
Owner

Originally created by @docrinehart on 7/21/2017

After deploying to Azure from VisualStudio 2017, I can reach my azure website and see the "Loading..." html page that bootstraps my react/redux application. However, the javascript doesn't ever kickoff the Single-Page App, and there are no errors I see in the js browser console or in the azure logs. I'm not exactly sure where to start debugging this and can't seem to find any related issues googling around.

My app is based around the yeoman generator for aspnetcorespa, so I am planning to try and deploy the base app template from a fresh generation to see if I experience the same problem. This will help me determine if it's the app or Azure, but I have the feeling it's on the app side -- in which case I'm not sure exactly what to start looking at since I have no errors to work with. I did update the Node appsetting in Azure to ensure I'm running the same version of node that I am locally (7.5.0) and confirmed it was up-to-date in the Azure console. I also can see the main-client and vendor js files are being pulled down when the page loads.

Everything runs fine locally, only seeing this once it's deployed to Azure.

*Originally created by @docrinehart on 7/21/2017* After deploying to Azure from VisualStudio 2017, I can reach my azure website and see the "Loading..." html page that bootstraps my react/redux application. However, the javascript doesn't ever kickoff the Single-Page App, and there are no errors I see in the js browser console or in the azure logs. I'm not exactly sure where to start debugging this and can't seem to find any related issues googling around. My app is based around the yeoman generator for aspnetcorespa, so I am planning to try and deploy the base app template from a fresh generation to see if I experience the same problem. This will help me determine if it's the app or Azure, but I have the feeling it's on the app side -- in which case I'm not sure exactly what to start looking at since I have no errors to work with. I did update the Node appsetting in Azure to ensure I'm running the same version of node that I am locally (7.5.0) and confirmed it was up-to-date in the Azure console. I also can see the main-client and vendor js files are being pulled down when the page loads. Everything runs fine locally, only seeing this once it's deployed to Azure.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/JavaScriptServices#558
No description provided.