-
Notifications
You must be signed in to change notification settings - Fork 29
Application fades to blank grey screen after loading animation #112
Comments
Having this same problem as well. Have tried reinstalling, launching with Spotify uninstalled. Not sure. It lets me install and open the app, I log into my Spotify acct, then it fades to blank :( |
Spotify PWA Seems to have had a server side change, breaking it completely on Edge legacy WebView. Currently trying to find a workaround. |
This also happens to me. Glad its being looked at! :) |
Any temporary workaround for now? Been waiting for almost a month (not asking for ETA). |
Same here. Do we at least know whats wrong? Is it possible for us to make a PR for this? |
Following! |
The problem is, Spotify seems to have dropped support for Edge Legacy in their PWA. Previously there were minor stuff that I was able to fix on-the-fly, but now it simply won't load at all and I can't seem to find a workaround for that. I also have a prototype of Xpo Music available on WinUI 3.0 Preview 2 (on branch vnext), but that needs Edge Beta to be installed, so that can't be used either. Not sure if this is still the case with WinUI 3.0 Preview 3, going to try it soon. And if anyone can find a workaround for open.spotify.com to open on Edge Legacy (temporarily, until WebView2 is finalized) I really appreciate that. |
WebView2 seems to have been finalized: |
i have same problem |
Any updates ? |
Not sure if this has been abandoned now? |
Same issue here. My Edge is not legacy however.. |
Last commit 6 months ago, and seeing as it's basically been unusable since the edge transition, I'd say it's been abandoned. |
First of all, I've had many issues installing XpoMusic, which are probably not fault of the app itself, but rather of my windows setup.
I've figured these out, and now I have this problem.
The login works fine, but when the loading animation is finished, there is just a blank screen. It doesn't react to media controls either.
I'm using v2.1.6.0, but I've also tried v2.1.3.0
The text was updated successfully, but these errors were encountered: