Error HRESULT e_fail has been returned from a call to a COM component
when double-clicking Package.appxmanifest
#19137
Labels
area/vswin
Categorizes an issue or PR as relevant to Visual Studio for Windows
difficulty/medium 🤔
Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI
kind/bug
Something isn't working
project/core-tools 🛠️
Categorizes an issue or PR as relevant to core and tools
Current behavior
Upon double-clicking the
Package.appxmanifest
file in an Uno project an error is thrown and dialog shown to user:Expected behavior
No error is thrown and
Package.appxmanifest
is loaded.How to reproduce it (as minimally and precisely as possible)
Load this SLN:
https://github.com/DragonSpark/Framework/blob/issues/reported/uno/19066/The%20DragonSpark%20Framework.sln
Then double-click this file in Visual Studio:
https://github.com/DragonSpark/Framework/blob/issues/reported/uno/19066/UnoApp1/UnoApp1/Package.appxmanifest
Workaround
None Known
Works on UWP/WinUI
None
Environment
Other
NuGet package version(s)
SDK 5.5.56
Affected platforms
Windows (WinAppSDK)
IDE
Visual Studio 2022
IDE version
Microsoft Visual Studio Community 2022 (64-bit) - Current Version 17.12.3
Relevant plugins
No response
Anything else we need to know?
Thank you for your efforts out there. 🙏
I have reported this here to Visual Studio:
https://developercommunity.visualstudio.com/t/Error-HRESULT-e_fail-has-been-returned/10819926
Upon searching I found this issue:
https://developercommunity.visualstudio.com/t/Continually-getting-Error-HRESULT-E_FAI/10733627
And this issue:
https://developercommunity.visualstudio.com/t/Double-clicking-on-a-PackageAppxmanifes/10658683
Seems like this is a recurring/common issue with Uno and upon creating a new SLN from the project generator everything works as expected and I am able to view/design the
Package.appxmanifest
file.Because of this I am wondering if there is something to do with my framework. 🤔 So, reporting here as well in case there is something Uno-related.
The text was updated successfully, but these errors were encountered: