SOLVED

Installed PWA - blank screen on launch

Copper Contributor

I have a web PWA at https://ourcardgame.ca

 

After opening it in Edge, the option (icon with plus symbol) to install the App appears in the address bar.  Clicking that and choosing "Install" works fine.  The PWA opens in a stand alone window.  Later, if I use Edge to visit the same site, the address bar shows an icon with a tooltip of "To open this link, choose an app". Clicking that icon opens the standalone window with the PWA running in it.  That works fine.

 

However, if I later click the Windows 10 start menu and click on the icon to start the PWA, the window opens and is completely blank.  If I open the DevTools window, the network log seems to be fine and shows evidence that the index.html file is loaded along with resources referenced in that file.

 

But the screen is blank.

 

As before, if I first open the web page and click to open it in the app, it opens the window and works fine.

 

Any ideas?

3 Replies

@glenlittle 

I saw what you have said and I am also seeing the same. I would recommend you send feedback through the in-app feedback tool(Alt+Shift+I) in Microsoft Edge with the diagnostics data attached which will help the PWA team to look after and resolve your issue.

@TheShaunSaw Thanks for the suggestion. I've done that now.

best response confirmed by glenlittle (Copper Contributor)
Solution

It turns out that the problem was in the PWA's manifest.json file as described here: https://stackoverflow.com/questions/54928050/vue-pwa-blank-screen-after-closing-the-app

 

By default, the manifest file had "./index.html" as the start URL.

{
 "start_url": "./index.html"
}  

 

Changing that to be "/" resolved the problem.

1 best response

Accepted Solutions
best response confirmed by glenlittle (Copper Contributor)
Solution

It turns out that the problem was in the PWA's manifest.json file as described here: https://stackoverflow.com/questions/54928050/vue-pwa-blank-screen-after-closing-the-app

 

By default, the manifest file had "./index.html" as the start URL.

{
 "start_url": "./index.html"
}  

 

Changing that to be "/" resolved the problem.

View solution in original post