Open evertonstz opened 5 years ago
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.
Interesting. Can you clone the project, install the dependencies with
npm install
and runnpm 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...
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.
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.
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.
Can you try the branch issue-13-test
to see whether a local file loads correctly?
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"
Ok, next up we'll check if google.com gets loaded correctly. Please pull from issue-13-test
again and test again.
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 :/
@evertonstz, have you ever encountered this issue again?
@evertonstz, have you ever encountered this issue again?
No, it's working all fine for 2 weeks now.
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.