Video sources not loading.

[Blackbluue]

For the past few days I have noticed that no video with a Crunchyroll source is loading. All I get is a spinning wheel, then after a long wait I get icons linking to the source on each respective website. The links still work and are directing me to the webpage, but the video source will not load in the app.

This occurs when trying to view videos from my queue and when looking at the anime's page directly. Clearing the cache using the in-app menu option does not help

Specs:

• OS: Windows 10
• Version 1.4.18, also occurred on version 1.4.16
  Screenshots
  

[Adam Haglund]

Have you tried logging out and back in again?

[Blackbluue]

When the problem first aroused, I did try that and it didn't work. However, after waiting a few hours and checking the app again it started to work like normal. I didn't do anything to it, it just started working. Not sure why. My app has been acting funny for a while now with no real explanation, I'll just Chalk it up to random circumstance.

[Adam Haglund]

Could be Crunchyroll going down temporarily. 🤷

[Nathaniel van Diepen]

This is happening to me today. I've already tried logging out/in and rebooting my machine. Crunchroll seems to be up as I can use their website as well as the android app. Only one item in my queue seems to load properly (Food Wars! The Second Plate).

I've tried running from a terminal to see if there is any useful output, but it looks like all I'm seeing is some deprecation warnings and an error when closing the application:

(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
(node:334925) ProtocolDeprecateCallback: The callback argument of protocol module APIs is no longer needed.
(node:334925) ProtocolDeprecateCallback: The callback argument of protocol module APIs is no longer needed.
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
TypeError: Cannot read property 'write' of null
    at e.exports.send (/tmp/.mount_yuna-anmbeQD/resources/app.asar/background.js:2:338340)
    at e.exports.close (/tmp/.mount_yuna-anmbeQD/resources/app.asar/background.js:2:338367)
    at e.exports.destroy (/tmp/.mount_yuna-anmbeQD/resources/app.asar/background.js:2:336548)
    at Ya.destroy (/tmp/.mount_yuna-anmbeQD/resources/app.asar/background.js:2:542727)
    at /tmp/.mount_yuna-anmbeQD/resources/app.asar/background.js:2:550308
    at App.<anonymous> (/tmp/.mount_yuna-anmbeQD/resources/app.asar/background.js:2:550330)
    at App.emit (events.js:215:7)
    at App.EventEmitter.emit (domain.js:476:20)
    at App.topLevelDomainCallback (domain.js:131:23)
    at electron/js2c/browser_init.js:6757:67

Remote debugging doesn't seem to provide any more information either. Then again it's been a while since I've played with electron so I'm not really digging into it as far as I could.

I wouldn't mind doing some more digging if you could provide me with more information on what to try.

Edit: Well after resuming from hibernation it's now populating properly, all but one newly added item to my queue:

[Adam Haglund]

Yeah I still can't reproduce it.

[Nathaniel van Diepen]

Yeah I still can't reproduce it.

Any suggestions on debugging steps to take that would provide you with more to go on?

[Adam Haglund]

Since we have nothing to go on still, nope. It seems to just randomly happen. 😕