OBS Studio not exporting in package list

[mariobrostech]

Brief description of your issue

While other winget packages successfully export when running the winget export command, OBS Studio doesn't successfully add itself to the list of packages. The winget export command displays this in its output. This is abnormal behavior, considering that OBS Studio lists a valid version number in winget and doesn't have any issues performing upgrades when a new version is released.

Steps to reproduce

Run winget export -o packages.txt, where packages.txt is the location of the destination package file. The command will run, but winget will show OBS Studio failing to be added to the package file, and when the file is opened, this behavior can be confirmed.

Expected behavior

I expect winget to be able to export OBS Studio, along with the rest of my installed programs, to a package file when the winget export command is run.

Actual behavior

winget fails to add OBS Studio to the package file, outputting the following error message: Installed package is not available from any source: OBS Studio.

Environment

Windows Package Manager v1.1.13405
Windows: Windows.Desktop v10.0.19044.1526
Package: Microsoft.DesktopAppInstaller v1.16.13405.0

[Trenly]

I believe this is an issue related to #147

The reason it seems to not export is because it cannot disambiguate between OBSProject.OBSStudio and OBSProject.OBSStudio.Prerelease. Since it can’t definitively determine which of the packages is installed, it reports it as unavailable.

Edit:

• Related to Use installed version for package disambiguation #1951
• Related to Enhancements to list command #1155
• Related to Improve matching logic with multiple sources #1663

[JerryWinkler]

I have the same issue.
Further, running "winget list" doesn't show winget as the Source for OBS Studio despite installing it from winget.

Same problem of not being able to export, and not being listed as winget as the Source for other programs such as voidtools.Everything and Zoom.Zoom.