You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems #209 is still present, at least with some app ids. We're encountering it at https://github.com/flathub/org.telegram.desktop. We sadly can't use <launchable> tag as it's just not known at build time what the desktop id will be as both snap and flatpak rename .desktop and .metainfo.xml files according to their rules. It seems the specification doesn't define how exactly the desktop id should be discovered, could it ignore the <id> tag and use the app_name?
It seems #209 is still present, at least with some app ids. We're encountering it at https://github.com/flathub/org.telegram.desktop. We sadly can't use
<launchable>
tag as it's just not known at build time what the desktop id will be as both snap and flatpak rename .desktop and .metainfo.xml files according to their rules. It seems the specification doesn't define how exactly the desktop id should be discovered, could it ignore the<id>
tag and use the app_name?Like
It would also be ok if the g_str_has_suffix check is just removed I guess, I just don't see how to make both flatpak and snap happy otherwise...
The text was updated successfully, but these errors were encountered: