Closed fstutzman closed 8 months ago
The problem with this exception is that it is a failed Win32 API call and there is no way to find out the details. We can only guess at some conditions - for example, when the application is minimized or hidden, when Windows is hibernating, or some other unique environment conditions in which the application is still running, but the user is not directly interacting with it
I removed this exception in the latest release because it doesn't provide any benefit. https://github.com/HavenDV/H.NotifyIcon/commit/10e6f835161bfa7a2f16d91a6bc13955491b43dc
If there are no side issues here with updating the icon (which can sometimes have the wrong state, for example), then this can be closed
@HavenDV I will pass your feedback to our Windows lead and see if there is any followup, and respond accordingly. Thank you for your quick response.
@HavenDV Thank you, we discussed this and we will update to the latest version. I will go ahead and close this.
Describe the bug
We are receiving multiple crash reports from our crash reporting system (Appcenter), I will include the crash below.
What is interesting about this issue is we are not hearing about the crash from users. WIth over 450 reports of the crash, it would expect some users to write in and complain that the icon disappeared or the program crashed. But we are not hearing these reports.
Steps to reproduce the bug
We are not able to reproduce the bug, which is confusing.
Expected behavior
No response
Screenshots
No response
NuGet package version
2.0.123
Platform
WPF
IDE
Visual Studio 2022
Windows Version
Windows 11, Windows 10
WindowsAppSDK Version
1.0
WindowsAppSDK Type
Packaged
Manifest
No response
Additional context
If anyone else is running into this crash, or has any other information on the trace, it would be much appreciated. Thank you.