Closed LuckyBeetle closed 1 year ago
Hi @LuckyBeetle , you can see Microsoft.AppCenter.Utils ApplicationLifecycleHelper
in your logs because it has an error catching logic. It isn't related to the crash itself.
I would suggest to add analytics to your app to help identifying the place of the issue. In your case the error message A method was called at an unexpected time
could be related to using async operations. Also worth checking the class LocalizeView
, as it is mentioned in the error message.
I'm closing it as not an SDK issue, but feel free to ask any additional questions.
Hi @LuckyBeetle , you can see
Microsoft.AppCenter.Utils ApplicationLifecycleHelper
in your logs because it has an error catching logic. It isn't related to the crash itself.I would suggest to add analytics to your app to help identifying the place of the issue. In your case the error message
A method was called at an unexpected time
could be related to using async operations. Also worth checking the classLocalizeView
, as it is mentioned in the error message.I'm closing it as not an SDK issue, but feel free to ask any additional questions.
Thank you for the feedback! I will try to add analytics to get more information. By the way 'LocalizeView' is not a part of my code and I can not locate its origin.
Description
In my Windows UWP app I receive regular crash report that I can not really figure out how to fix. Based on the call stack trace it feels it could be related to the SDK.
Repro Steps
I can not figure out how to reproduce it.
Details
Here is a crash:
CallStack available:
It happens the most on windows versions 10.0.2200, 10.0.19045, 10.0.19044 I have latest SDK installed and targeting Windows platform 2004