Custom CAs fail TLS handshake ("Unable to connect to host") / Need option to trust self-signed certs

[RaspberryKitty1]

Description

When trying to connect Fladder to a local Jellyfin server running on HTTPS with a custom/self-signed Certificate Authority (e.g., *.raspberry.lan), the app fails to connect and throws an "Unable to connect to host" / "Invalid URL" error.

Because Flutter's underlying networking stack (dart:io / BoringSSL) does not import Android's User Credential trust store, custom Root CAs installed on the OS are ignored during the TLS handshake. Furthermore, Fladder does not currently provide a setting to allow self-signed certificates or bypass SSL verification errors.

Additional Context (Cross-Platform Comparison):

• Fladder Desktop (Windows / macOS / Linux): Works 100% using https://jellyfin.raspberry.lan:8920 because Dart on desktop evaluates the host OS trust store where the Root CA is installed.

Reproduction steps

Set up a local Jellyfin instance behind HTTPS using a local CA / self-signed certificate (e.g., [https://jellyfin.raspberry.lan](https://jellyfin.raspberry.lan)).

Install the local Root CA onto the Android device under Settings → Security → User Credentials.

Verify that the native Jellyfin Android app connects successfully using this domain.

Open Fladder and attempt to log in using [https://jellyfin.raspberry.lan:8920](https://jellyfin.raspberry.lan:8920).

Screenshots

Logs

Platform

Android

App Version

0.10.3

Jellyfin server

jellyfin 10.11.11+deb13 (Debian 13)