This content is likely not relevant anymore. Try searching or browse recent questions.
Chromecast crashes using Service Workers / Deep C++ Firmware Bug? 0 Recommended Answers 3 Replies 3 Upvotes
Last edited 10/23/19
I filed a bug report on Issuetracker #143057613 but I noticed that there are more than 17 unanswered issues and I have low hopes that they will fix it anytime soon, that's why I'm posting it here to see if someone got more information regarding this problem/bug.
Chromecast receivers crashes "Something went wrong" when calling a service worker.
Tested on 1st and 2nd gen, ultra and TV build-in cast devices with latest firmware versions 1.42.172094 or 1.36154871.
When calling the
It would be nice of someone from the cast developers team could take a look into this issue.
Kind regards,
Joey
PS: The script in the
Chromecast receivers crashes "Something went wrong" when calling a service worker.
Tested on 1st and 2nd gen, ultra and TV build-in cast devices with latest firmware versions 1.42.172094 or 1.36154871.
When calling the
​navigator.serviceWorker.register('serviceworker.js') the cast device will instantly crash without throwing any errors except for "Something went wrong" on the TV
Multiple receiver applications that uses the service workers stopped working because of this update.
Some people suggested that this could be a deep C++ bug in the chromecast firmware.
Here is the code snippet that worked before the firmware update, and now it crashes:
( Tested on both v2 and v3 cast receiver framework )
Multiple receiver applications that uses the service workers stopped working because of this update.
Some people suggested that this could be a deep C++ bug in the chromecast firmware.
Here is the code snippet that worked before the firmware update, and now it crashes:
( Tested on both v2 and v3 cast receiver framework )
if ('serviceWorker' in navigator) { navigator.serviceWorker.register('serviceworker.js', {scope: './'}).then(() => { console.log('Service worker registered, starting receiver context') const ctx = cast.framework.CastReceiverContext.getInstance(); ctx.start() }).catch(err => { console.log(err); })}
It would be nice of someone from the cast developers team could take a look into this issue.
Kind regards,
Joey
PS: The script in the
service worker is irrelevant, even if it's empty it won't even execute because the cast devices crashes before registering the service worker. This question is locked and replying has been disabled.
Link to post
Delete post?
This will remove the reply from the Answers section.
Notifications are off
Your notifications are currently off and you won't receive subscription updates. To turn them on, go to Notifications preferences on your Profile page.