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
I created .winget file pointing to private store app. This will fail the Store access from winget, because i need to log in to the store.
Error:
Apply :: WinGetPackage
The configuration unit failed while attempting to test the current system state.
An error occurred while searching for packages: CatalogError
My issues:
CatalogError: This is pretty cryptic. Why not just say we cannot access the Source if that is the issue.
""
Why make me do extra work when winget can tell me:
OPTIONS
A)
See C:\Users\WDAGUtilityAccount\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\WinGet-2024-04-11-09-03-54.698.log
for additional details.
B) suggest, Re-Run the command with the --Logs and --verbose-logs for additional details.
C) Simply tell the user what is wrong so they do not need to look at the log.
Steps to reproduce
In SandBox, run the following .winget once you have updated the id to be canary build of a store app that requires permission
C:\Users\WDAGUtilityAccount>winget --info
Windows Package Manager v1.7.10861
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.26100.1000
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10861.0
The text was updated successfully, but these errors were encountered:
Brief description of your issue
I created .winget file pointing to private store app. This will fail the Store access from winget, because i need to log in to the store.
Error:
Apply :: WinGetPackage
The configuration unit failed while attempting to test the current system state.
An error occurred while searching for packages: CatalogError
My issues:
Why make me do extra work when winget can tell me:
OPTIONS
A)
See C:\Users\WDAGUtilityAccount\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\WinGet-2024-04-11-09-03-54.698.log
for additional details.
B) suggest, Re-Run the command with the --Logs and --verbose-logs for additional details.
C) Simply tell the user what is wrong so they do not need to look at the log.
Steps to reproduce
In SandBox, run the following .winget once you have updated the id to be canary build of a store app that requires permission
properties:
configurationVersion: 0.2.0
resources:
allowPrerelease: true
description: private app
resource: Microsoft.WinGet.DSC/WinGetPackage
settings:
id:
source: msstore
Expected behavior
Better error handling. see suggestions
Actual behavior
Environment
The text was updated successfully, but these errors were encountered: