-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packages from "msstore" source aren't visible in list
or export
#1562
Comments
list
or export
The store source is a front end for existing technologies. The "Id" values simply need to be unique rather than human readable. We do have work coming to improve these, but it's more for us humans to be able to make some sense out of them 😁. I have commented on other issues the state of "list". We have a couple of other related issues we're working on to improve the matching logic so we can bring the matching source back for "list" and subsequently "export". Related to:
I will change the title of this issue to capture "list" and "export" since you were the first to report it in a top level ask. |
list
or export
list
or export
It used to work before when store support was experimental. Did the addition of all store apps mess it up? |
The earlier experimental source was just a subset of packages that had been curated. The new source combines several back end systems into a unified REST source implementation the Windows Package Manager can interact with. We're actively making improvements on the search experience, and the mapping between entries in the store and how they are installed in Apps and Features. As soon as the correlation has been improved, we will re-enable the list and export commands for the "msstore" source. |
Hi @denelon . I was just wondering what was the ETA on this one ? |
@TechWatching I don't have an ETA on this one. We're working on several improvements to matching. The current behavior supports export if the package from the store was installed via winget. We are working on improvements to validation to help enrich the manifests in the "msstore" source to include the "AppsAndFeatures" entries so we can have higher confidence. The back end for the "msstore" source is quite different than the "winget" source. We've been working with the Microsoft Store teams to improve the experience all up. We requested getting version as a higher priority so the upgrade flow and a couple of other scenarios work better for the store-based Win32 packages. |
I just tried a {
"$schema" : "https://aka.ms/winget-packages.schema.2.0.json",
"CreationDate" : "2022-10-19T13:14:09.586-00:00",
"Sources" :
[
{
"Packages" :
[ // cut for brevity
{
"PackageIdentifier" : "Microsoft.PowerShell"
}
],
"SourceDetails" :
{
"Argument" : "https://cdn.winget.microsoft.com/cache",
"Identifier" : "Microsoft.Winget.Source_8wekyb3d8bbwe",
"Name" : "winget",
"Type" : "Microsoft.PreIndexed.Package"
}
},
{
"Packages" :
[
{
"PackageIdentifier" : "9PKJV6319QTL"
}
],
"SourceDetails" :
{
"Argument" : "https://storeedgefd.dsx.mp.microsoft.com/v9.0",
"Identifier" : "StoreEdgeFD",
"Name" : "msstore",
"Type" : "Microsoft.Rest"
}
}
],
"WinGetVersion" : "1.4.2161-preview"
} This matches with what Also, |
The "one" entry you have is likely to have been installed via WinGet. We're still doing some heavy lifting to improve matching against the "msstore" source. We were getting too many "false positives" in terms of matching entries from the "msstore" store source, so we disabled the global matching in |
When running We have an Issue tracking improvements to make it work more like a filter: |
Is there an update on this issue? I just did an export and still none of the Store apps were exported, just the winget ones. |
Brief description of your issue
When I run
winget search
for an MS Store app, all the apps from the store show IDs that are just a sequence of numbers and capital letters of fixed length. Winget also doesn't show any source for MS Store apps withwinget list
.Steps to reproduce
winget search Whiteboard
Expected behavior
The MS Store apps have their MS Store IDs as the IDs in winget.
Actual behavior
Example:
Environment
The text was updated successfully, but these errors were encountered: