[BUG] Firefox and Zen Browser show a raw app ID instead of the app name/icon in Media Flyout

[hideloll]

Describe the bug

Description

When playing media in Firefox-based browsers (Firefox and Zen Browser), Fluent Flyouts displays a raw application ID (for example, F0DC299D809B9700) instead of the browser's name in the media flyout.

All media controls and metadata (such as the title and playback controls) work correctly—the only issue is that the application name is replaced with the raw ID.

Expected behavior

The media flyout should display the application name (e.g. Firefox or Zen Browser) just like it does for Chromium-based browsers.

Actual behavior

The media flyout displays a raw identifier such as F0DC299D809B9700 instead of the browser name.

Environment

• Windows 11 25H2
• Latest version of Fluent Flyouts
• Latest version of Firefox
• Latest version of Zen Browser

Additional information

• The native Windows 11 media flyout correctly identifies both Firefox and Zen Browser by name.
• Chromium-based browsers (such as Chrome and Edge) display their application names correctly in Fluent Flyouts.
• The issue appears to affect Firefox-based browsers only.

To Reproduce

1. Open Fluent Flyouts.
2. Launch Firefox or Zen Browser.
3. Play any media (e.g. a YouTube video or music).
4. Trigger the media flyout (e.g. by pressing a volume key or opening the media flyout).
5. Observe that the application name is displayed as a raw identifier (e.g. F0DC299D809B9700) instead of "Firefox" or "Zen Browser".

Logs, screenshots & additional context

The media session is detected correctly (title, playback controls, etc. are displayed), so this does not appear to be an SMTC metadata issue. Only the application name is affected. The native Windows 11 media flyout correctly displays "Firefox" and "Zen Browser," while Fluent Flyouts displays a raw identifier (e.g. F0DC299D809B9700).

FluentFlyout Version

v2.13.1

Windows Version

Windows 11 25H2

Architecture

x64

Checklist

• I have searched that there is no existing bug report regarding my issue
• I have read the FAQ and there is no answer to my issue

[zen1337th]

Thank you for reporting this. As a Firefox user myself I haven't noticed this somehow...

I have created PR #951 which resolves this issue.