The "SSL handshake failed: Unable to get local issuer certificate" error occurs because the root certificate required to validate the SSL certificate is missing, so a system related issue and not a bug in Strawberry.
Flatpak sandbox is strictly isolated and does not automatically read SSL/TLS certificates from the host system's trust store, it's probably a bug in the runtime, missing the root certificates, could be this bug: https://invent.kde.org/packaging/flatpak-kde-runtime/-/work_items/91

@athoopen Great! Glad you solved it!

@silver-sun thank you for notifying me

The "SSL handshake failed: Unable to get local issuer certificate" error occurs because the root certificate required to validate the SSL certificate is missing, so a system related issue and not a bug in Strawberry.
Flatpak sandbox is strictly isolated and does not automatically read SSL/TLS certificates from the host system's trust store, it's probably a bug in the runtime, missing the root certificates, could be this bug: https://invent.kde.org/packaging/flatpak-kde-runtime/-/work_items/91

Thank you, Jonas. I don't know how I missed that thread when I was looking, sorry! Also, my browser is Firefox.

After reading more, would upgrading my OS from Mint 21.3 to Mint 22 likely mean I don't have any of these issues in the first place? Or installing using something other than flatpak? I don't particularly mind what method I use to install/run it.

And more information on the things I tried/looked at, below for more context/information (if relevant)

I don't have anything for strawberry at /usr/share/applications/strawberry.desktop sudo find /usr -type f -name 'strawberry' returns nothing xdg-open tidal://test does nothing. However, flatpak run org.strawberrymusicplayer.strawberry tidal://test does add tidal://test.
(My understanding is all this is expected if one installed via flatpak?)

I ran some commands to create a wrapper script/desktop handler (I didn't write any of it; I'm not an expert on this stuff). After doing that, xdg-open "tidal://test" started working and would add it to the playlist, but I would run into the same SSL handshake error that others are posting in other threads. I undid those commands after because they hadn’t solved the problem.

@silver-sun Well, if anything, it means it'll be worthwhile for me to downgrade to a previous version until this gets a fix.
It's such an odd omission.

Tested again today with the latest. I also looked into each album that ended up getting put into the various artists folder incorrectly.

It seems that the sync to device feature takes into account ALL tracks in an album regardless if they are all being synced or not.

What I would like strawberry to do is only consider the information of the tracks being synced to the device when applying the sync options.

Here's the log since I couldn't attach it, and was too long to post:

https://paste.chapril.org/?51e9191f2cfea3aa#67PWAeg8BnH3uVySzJRUZU2WJXoPJKR8TnEfHFip2KWq

Please note that 13:47:47.291 DEBUG Database:561 Starting database backup seems to never finish.

I closed Strawberry at 14:05:01.037

@zayyad
The song needs to be a local file in the collection, make sure there is a vinyl icon next to the Source column in the playlist, it indicates that it is in the collection.

@arterial
Make sure ALSA or PulseAudio is selected as output in Tools / Settings / Backend, with PipeWire it will use the ALSA, or PulseAudio emulation. Don't select pipwire as output, the PipeWire output doesn't work properly, it's unfinished/buggy.

@Hoshiet
Change some columns, then go to Music / Quit, re-open Strawberry, are they then saved?
if not, please do a backtrace so we can see if it crashes:
https://wiki.strawberrymusicplayer.org/wiki/Backtrace
Or use coredumpctl list and check if it crashed previously.

@thats_a_movie
The new version 1.2.22 released now has an option for dark mode under the appearance settings, you can also configure each individual color on the interface.