WPF Desktop bridge app does not report crashes to the AppCenter

[marekdovjak]

Description

We have a WPF application, which is distributed in the MSStore using the Windows Desktop bridge. While the application is tested as pure WPF app, it's properly reporting crashes to the AppCenter. But after packaging the exact same app using the Desktop bridge, crashes are no logner reported.

After enabling the Verbose log level and generating test crash, I can see there are 0 crash reports detected. I also checked the Logs.db file in user's AppData folder, table LogEntry doesn't contain any crash reports. It contains few core/analytics records, which are correctly sent to the AppCenter after running the app.

Repro Steps

1. Create simple wpf app project with the appcenter sdk
2. Generate test crash
3. Verify the crash is reported to the AppCenter
4. Add Windows Application Packaging project for the wpf app to the solution
5. Run the Packaging project
6. Generate test crash
7. Crash is not reported to the AppCenter

Details

Platform: Win10, WPF, NET 7.0, Desktop Bridge SDK version 5.0.2 OS: Windows 10/11 Visual Studio Version 17.6.0

Workaround

I used the DispatcherUnhandledException += App_DispatcherUnhandledException; and

void App_DispatcherUnhandledException(object sender, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs e)
{
    Crashes.TrackError(e.Exception);
}

as recommended in this issue https://github.com/microsoft/appcenter-sdk-dotnet/issues/1727, so crashes are reported as errors now.

[DmitriyKirakosyan]

Hi @marekdovjak , thank you for this report. I believe it is a duplicate of https://github.com/microsoft/appcenter-sdk-dotnet/issues/1727.

We already merged the fix and currently preparing the release. It should be available today or tomorrow. I'm closing it as a duplicate.

[marekdovjak]

@DmitriyKirakosyan I don't think it's duplicate. For wpf app, everything is working well. We have problems when packaging the wpf app with Windows Desktop Bridge.

After upgrading the AppCenter SDK to 5.0.2, problem still persits

[DmitriyKirakosyan]

Thank you for testing on new version and confirming the issue persists. We will investigate it.

You mentioned that using DispatcherUnhandledException works well for you as a workaround. In the latest version we added DispatcherUnhandledException event listener for catching exceptions, so I would expect it should resolve your issue...

[MikhailSuendukov]

Hello, I tried to reproduce your error, but when running a WPF application using Windows Application Packaging, crashes are successfully sent to the AppCenter portal. For further investigation, a small demo application that reproduces your error would be very useful to us.

[marekdovjak]

@MikhailSuendukov I realized that the steps I wrote to reproduce the problem were not complete. You have to use the Target Framework Moniker option. So instead of <TargetFramework>net7.0-windows</TargetFramework> use <TargetFramework>net7.0-windows10.0.17763.0</TargetFramework> or similar.

There's simple demo app in the attachment. With the moniker option, crashes are not reported.

WpfApp1.zip

[MikhailSuendukov]

Thank you very much for your demo app, indeed your bug is reproducible on this app. In that case, I will create a work item on our board and keep you updated on progress.

[DmitriyKirakosyan]

The fix was released, so I'm closing it.

[marekdovjak]

@DmitriyKirakosyan I did a quick test with the sample app I provided earlier and appcenter 5.0.3 - it still doesn't work with the target WapProjTemplate1 (desktop bridge).

[MikhailSuendukov]

Hi, I was able to reproduce the error, apparently the SDK incorrectly determines the type of the wrapped application, so I created a draft pull request to fix the bug.

[sebaJoSt]

when is the next release with this bug fix planned?

[30797593]

when is the next release with this bug fix planned?

[30797593]

I am encountering the same issue. The project, packaged as a WPF and uploaded to the Microsoft Store, can collect reports in its pure WPF form, but once packaged with the Desktop Bridge, it no longer can.