v1.13.0: YouTube streaming provider fails to register - No streaming provider available

[ClassyMan]

Description

Fresh install of Nuclear v1.13.0 (.deb, Linux x86_64). The YouTube plugin loads and reports as enabled, but the streaming provider never actually registers. Every track in the queue shows "Playback error" and nothing plays.

The Spotify metadata plugin (nuclear-plugin-something) works fine — search results, album art, artist info all load correctly. Only the streaming side is broken.

Steps to Reproduce

1. Install nuclear-music-player_1.13.0_amd64.deb on a fresh system
2. Launch Nuclear — YouTube and "something" plugins auto-install from the store
3. Search for any artist/album
4. Add tracks to queue
5. Attempt playback

Expected Behavior

YouTube streaming provider registers and tracks play.

Actual Behavior

All queued tracks show "Playback error". No audio plays.

Logs

From ~/.local/share/com.nuclearplayer/logs/nuclear-music-player.log:

[INFO] [plugins] Plugin nuclear-plugin-youtube@0.1.0 loaded successfully
[INFO] [plugins] Plugin nuclear-plugin-youtube enabled
[INFO] [plugins] Plugin nuclear-plugin-something@0.1.0 loaded successfully
[INFO] [plugins] Plugin nuclear-plugin-something enabled
[WARN] [streaming] No streaming provider available
[INFO] [queue] Loaded 10 items from disk

The YouTube plugin's onEnable calls api.Providers.register() with a StreamingProvider (kind: streaming), but the streaming system never picks it up. This happens consistently across multiple restarts.

The metadata provider from nuclear-plugin-something (kind: metadata) registers and works fine — search and artist pages populate correctly.

Environment

• Nuclear version: v1.13.0 (a452lccd)
• OS: Ubuntu 24.04 LTS, kernel 6.17.0-14-generic
• Audio: PipeWire 1.0.5, Focusrite Scarlett 2i2
• yt-dlp: 2026.02.21 (with deno 2.7.1 as JS runtime)
• Install method: .deb from GitHub releases

Additional Context

• yt-dlp works correctly from the command line
• The Tauri/Rust backend has yt-dlp integration (src/ytdlp.rs) but it is never reached because the plugin's streaming provider does not register in the first place
• This appears to be a plugin SDK issue where api.Providers.register() silently fails for StreamingProvider types

[nukeop]

Does this happen only to the items that are in the queue when you quit and reopen? Or does nothing play?

[reddooneee]

I have the same problem, it appens in both case: when you have songs in the queue, and when you try to play other song.