-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
404 error on msstore endpoint resulting in Failed to update source: msstore
#4785
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
Feel free to mark as
Area-External
|
I believe it is package specific, as these are the relevant lines -
|
I was curious that if package metadata couldn't be found from source, then why didn't WinGet fallback to assigning it an ID of the form I tried to gain a deeper understanding by looking at the code, and though I can't understand all of it, I think what's happening is that the CLI tried to look into my winget-cli/src/AppInstallerRepositoryCore/CompositeSource.cpp Lines 1504 to 1536 in 19b3b5e
If the msstore response for a package is @denelon This may not be
Area-External
|
I had same issue. However when I uninstalled the package that MsStoreSource return 404, this app don't have run with any issues. |
…ponses (#5179) When searching for store source with id that's recently taken down, store source will return 404 instead of empty results (what winget-cli-restsource does). This will be treated as a source search error in our code. The fix is to treat 404 response with certain schema as empty result instead of failure. Tested manually with store source and added unit tests. fixes #4785, fixes #4784
Brief description of your issue
winget list
reports meFailed when searching source; results will not be included: msstore
. Looking in the CLI verbose logs, found that it gets a 404 when hitting msstore endpoint. Performing a source reset didn't help either.Relevant log snippet
Full log: WinGet-2024-09-03-23-43-25.211.log
Steps to reproduce
Not aware of any. Happens from time to time on my machine. Could be a CDN / my region issue
Expected behavior
Msstore source is updated successfully
Actual behavior
Failed when searching source; results will not be included: msstore
Environment
The text was updated successfully, but these errors were encountered: