[Bug]: Error: No valid URL to decipher

[ArthurKun21]

Guidelines

• [X] I have encountered this bug in the latest release of FreeTube.
• [X] I have encountered this bug in the official downloads of FreeTube.
• [X] I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
• [X] I have searched the documentation for information that matches the description of the bug I want to file, without success.
• [X] This issue contains only one bug.

Describe the bug

1. Click a video (there is no consistent video where I keep encountering the error)
2. Encounter the error

Expected Behavior

Be able to watch video

Issue Labels

content not loading

FreeTube Version

b2fe59d331289e0365f67e04e0186e17374b8d1c

Operating System Version

Windows 11 22635.3930

Installation Method

.exe

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

No response

Additional Information

Error: No valid URL to decipher
    at wF.decipher (renderer.js:2:1363128)
    at iD.decipher (renderer.js:2:1126826)
    at BN (renderer.js:2:1410819)
    at MN (renderer.js:2:1410695)
    at async r.getVideoIn

renderer.js:2 TypeError: Cannot read properties of undefined (reading 'primaries')
    at new iD (renderer.js:2:1125270)
    at PN (renderer.js:2:1404973)
    at r.createInvidiousDashManifest (renderer.js:2:1906203)
    at async renderer.js:2:1896383

TypeError: Cannot read properties of undefined (reading 'primaries')
    at new iD (renderer.js:2:1125270)
    at PN (renderer.js:2:1404973)
    at r.createInvidiousDashManifest (renderer.js:2:1906203)
    at async renderer.js:2:1896383

I actually have been encountering this issue for the past few days and just managed to capture it.

I have also been using Pikachu's shaka build and on there while I did not capture it, I am getting 403 error

navigating away and clicking the video again fixes the issue.

https://github.com/user-attachments/assets/a578562c-4a80-49a2-8828-f00cdd697f7f

Nightly Build

• [ ] I have encountered this bug in the latest nightly build.