I may have ranted about the state of OBS packaging on Linux before, specifically if you run it under Wayland or use any binaries not provided by the devs via Flathub or their Ubuntu repository.
The TL;DR is that that browser sources and docks don't work with Wayland due to their engine of choice being outdated and service integration for Twitch and YouTube don't work, because the devs cannot share the relevant API keys.
Both of these issues feel kinda unfair to blame on the OBS team, but I do take issue with the ungodly amount of digging I had to do in order to fully understand this and devise a worthwhile fix for myself.
What I'm about to tell you isn't top secret information, but there sure as shit isn't an easy to find, official guide that could massively help package maintainers and end users on Linux.
First, in order for the browser engine to work, Wayland users will have to force OBS through XWayland. I've ended up with this command:
env WAYLAND_DISPLAY="" obs
The API keys are obviously trickier and I'm only going to explain the process for YouTube here, because I no longer stream on Twitch and you see what happens when devs don't document their projects very well?
Anyway, you create a new project at console.cloud.google.com, add the Google account you use for YouTube as a tester and set up OAuth access, which should give you two strings, a client ID and a secret.
Now, depending on how you're going to compile OBS from source (yes, of couse you have to), CMakePresets.json might be a good place to enter this information. I did it in the PKGBUILD for the Arch AUR package obs-studio-liberty (pictured below), the respective hash values have to be set to zero.
