Skip to content
This repository has been archived by the owner on Oct 1, 2019. It is now read-only.

1.2 won't start, ethernal white screen #13

Open
evertonstz opened this issue Mar 21, 2019 · 11 comments
Open

1.2 won't start, ethernal white screen #13

evertonstz opened this issue Mar 21, 2019 · 11 comments
Labels
bug Something isn't working

Comments

@evertonstz
Copy link

I downloaded the latest released today in the ".pacman" format, removed the old one with "pacman -R" and installed the new one with "pacman -U". After installed, trying to launch the new version will only give me a window with pure white screen, nothing happens. I deleted the configuration folder at .config thinking the new version could be incompatible or maybe I corrupted it somehow, tried to launch again, same behavior. After that I downloaded the appimage, launched it, same behavior; deleted the .config again just in case, launched again, same behavior.

This behavior is kinda like the one at #7, the difference is that I don't get the error message.

@jgierer12
Copy link
Owner

Interesting. Can you clone the project, install the dependencies with npm install and run npm run start to start a dev build? If something is wrong it should show up either in the devtools or in the terminal you started it with.

@jgierer12 jgierer12 added the bug Something isn't working label Mar 21, 2019
@evertonstz
Copy link
Author

evertonstz commented Mar 21, 2019

Interesting. Can you clone the project, install the dependencies with npm install and run npm run start to start a dev build? If something is wrong it should show up either in the devtools or in the terminal you started it with.

I did it, after starting with npm it worked fine, no errors... I closed the dev build and started the version I have installed and... it worked like the bug never happened, lol. This is strange, could be related to a bad network connectivity? I'm in Brazil, we don't have the best internet out there...

EDIT: I think it's related with poor internet conectivity, I turned my wifi off and tried opening it, I got the same behaviour...

@jgierer12
Copy link
Owner

That's very likely, I currently don't have a timeout or message in place in case https://www.pocketcasts.com can't be reached.

@evertonstz
Copy link
Author

evertonstz commented Mar 21, 2019

Hmm, actually not related with the network it seems, here's it happening again, it's on debug, I can open the player on my firefox browser. I was finally able to get a log tho, here.

@jgierer12 jgierer12 reopened this Mar 22, 2019
@jgierer12
Copy link
Owner

Seems like the log is unrelated - I can reproduce that (by opening the Network devtools tab) and it seems to be an upstream electron issue. But the app continues to work as expected for me.

@jgierer12
Copy link
Owner

Can you try the branch issue-13-test to see whether a local file loads correctly?

@evertonstz
Copy link
Author

Can you try the branch issue-13-test to see whether a local file loads correctly?

Sorry for being a little late, had some work to do. Anyways, the local file loads fine, I get "Local file displaying correctly"

@jgierer12
Copy link
Owner

Ok, next up we'll check if google.com gets loaded correctly. Please pull from issue-13-test again and test again.

@evertonstz
Copy link
Author

Google loads, the probably is that pocketcasts is working again, I'll have to wait the bug happen again so I can test if google is really loading in the same scenario :/

@jgierer12
Copy link
Owner

@evertonstz, have you ever encountered this issue again?

@evertonstz
Copy link
Author

@evertonstz, have you ever encountered this issue again?

No, it's working all fine for 2 weeks now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants