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
After upgrading to AppCenter 5.0.1 the stacktrace of the exceptions is not being logged for a Windows App SDK 1.2 app, with AppCenter 4.5.3 all works fine.
Repro Steps
Please list the steps used to reproduce your issue.
Create a Windows App SDK 1.2 app
Add AppCenter 5.0.0 nuget and configure the app to log crashes
Throw an exception
Details
What is your app platform (Xamarin.Android or Xamarin.iOS or UWP)?
Windows App SDK 1.2
If using Xamarin.Forms or if using portable/shared code to call our SDK APIs, are you using shared project, PCL code or .NET standard code for the application? Which .NET standard version or which PCL profile?
.NET 6
Which SDK version are you using?
5.0.1
Which OS version did you experience the issue on?
Windows 10
What device version did you see this error on? Were you using an emulator or a physical device?
Physical
What third party libraries are you using?
Windows App SDK
The text was updated successfully, but these errors were encountered:
You are creating an UWP application on the App Center Portal, right? Is it possible for you to create a WPF app as a workaround? The stacktrace should work for WPF. The problem is backend doesn't recognize the stacktrace as a UWP's stacktrace.
At this moment we don't have a dedicated MAUI Windows application.
Hi @DmitriyKirakosyan, yes, we use an UWP application on the App Center Portal, I tried to create a WPF app but it doesn't work either when using App Center 5.0.1. With App Center 4.5.3 it is correctly registered in both type of App Center's apps.
Description
After upgrading to AppCenter 5.0.1 the stacktrace of the exceptions is not being logged for a Windows App SDK 1.2 app, with AppCenter 4.5.3 all works fine.
Repro Steps
Please list the steps used to reproduce your issue.
Details
The text was updated successfully, but these errors were encountered: