Folder / Sub-folder links into the media-browser are not working using navigate URL Handler

[lutzvahl]

Home Assistant Android app version(s):
2025.1.2-full

Android version(s):
Android 15

Device model(s):
Pixel 9

Home Assistant version:
Core
2025.1.2
Supervisor
2024.12.3
Operating System
14.1
Frontend
20250109.0

Last working Home Assistant release (if known):
N/a

Description of problem, include YAML if issue is related to notifications:

Folder / Sub-folder links into the media-browser are not working.
E.g. in the browser {externalURL}/media-browser/browser/app%2Cmedia-source%3A%2F%2Funifiprotect will open the Media Sources -> Unifi Protect Folder.
Using this URL as a clickAction in a Notification will open the Browser.

Using homeassistant://navigate as suggested in the wiki full URL homeassistant://navigate/media-browser/browser/app%2Cmedia-source%3A%2F%2Funifiprotect is showing an error
Invalid media source URI

Companion App Logs:
Can't see anything related in the logs. Please advise in case needed

Screenshot or video of problem:

[jpelgrom]

Looks like the app opens this as {external}/media-browser/browser/app,media-source://unifiprotect?external_auth=1 (viewed using Chrome remote debugging), so I guess Android and/or the app are decoding too much.

[lutzvahl]

Did you try to double encode the URL?

[jpelgrom]

No, I'm following your example?

[lutzvahl]

No, I'm following your example?

No worries!
I've tried using a double encoded URI: homeassistant://navigate/media-browser%2Fbrowser%2Fapp%252Cmedia-source%253A%252F%252Funifiprotect
but same error.

[lutzvahl]

Looks like the app opens this as {external}/media-browser/browser/app,media-source://unifiprotect?external_auth=1 (viewed using Chrome remote debugging), so I guess Android and/or the app are decoding too much.

@jpelgrom Any idea how to fix?

The same error occurs using the button action approach.

actions: - action: URI title: Open Url uri: >- homeassistant://navigate/media-browser%2Fbrowser%2Fapp%252Cmedia-source%253A%252F%252Funifiprotect

[jpelgrom]

The same error occurs using the button action approach

Yes, all deep links will show the same behavior because it is the same code, notifications or local or shortcuts or ...

No additional research yet, comment was just an observation and for future reference.