How to test & debug my app in other computers/configurations?
Hi, I get numerous reports from AppCenter that my app crashes frequently in some laptops, for example, Inspiron 7370. I have four pcs. I am unable to reproduce that bug in any of my pcs. so I want to know, how to test & debug my uwp app in other devices like mentioned before Inspiron 7370. It seems an essential feature to develop bug free apps. Thanks in advance.
Universal Windows Platform (UWP)
-
Fay Wang - MSFT • 5,221 Reputation points
2020-05-04T05:02:18.72+00:00 Does AppCenter provide any error code or error message when the app crashes? In addition, visual studio allows to deploy and debug your app remotely on other devices, for more details about this, you can refer to this document.
-
MG Bhadurudeen • 631 Reputation points
2020-05-05T04:25:22.403+00:00 The following are the Stack traces. I could not figure out which part of my code is responsible for this bug.
System.Exception: Layout cycle detected. Layout could not complete. Layout cycle detected. Layout could not complete. ComCallHelpers.Call ($__ComObject __this, RuntimeTypeHandle __typeHnd, Int32 __targetIndex) C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Packages\appcompile-20200417-081525-10484\AC\Temp\Ilc882687807\StudyAndPractice.McgInterop\SharedStubs.g.cs at 3376, line 5
-
MG Bhadurudeen • 631 Reputation points
2020-05-05T04:26:02.273+00:00 System.Runtime.InteropServices McgMarshal.ThrowOnExternalCallFailed (Int32 hr, RuntimeTypeHandle typeHnd) f:\dd\ndp\fxcore\CoreRT\src\System.Private.Interop\src\Shared\McgMarshal.cs at 1267:13 __Interop ComCallHelpers.Call ($__ComObject __this, RuntimeTypeHandle __typeHnd, Int32 __targetIndex) C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Packages\appcompile-20200417-081525-10484\AC\Temp\Ilc882687807\StudyAndPractice.McgInterop\SharedStubs.g.cs at 3376:5 __Interop.ForwardComStubs Stub_11<System.__Canon> (Void* InstParam, $__ComObject __this, Int32 __targetIndex) C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Packages\appcompile-20200417-081525-10484\AC\Temp\Ilc882687807\StudyAndPractice.McgInterop\SharedStubs.g.cs at 417:4 Microsoft.AppCenter.Utils ApplicationLifecycleHelper.<ctor>b__17_1 (Object sender, $UnhandledErrorDetectedEventArgs eventArgs) at 0
-
MG Bhadurudeen • 631 Reputation points
2020-05-05T04:26:11.097+00:00 Most affected OS 10.0.18362 38.7% 10.0.18363 35.5% 10.0.17763 25.8%
Top devices: HP Notebook 390, HP Laptop 15-da0xxx, Inspiron 15-3567Note: I don't get my app crashed in my 4 systems. so I am unable to guess which part causes this error!
Also, is there really no way to test my app on other devices that I don't have?
If there is no way, I would have to buy the top 1 or 2 devices, in which my app crashed, for this testing purpose alone. -
Fay Wang - MSFT • 5,221 Reputation points
2020-05-05T06:11:45.007+00:00 Have you tested your app in release mode? If you download it from store and test it, will the same issue occur? In addition, from the error information, there is something wrong in SharedStubs page, you can check the related code snippet from "SharedStubs.g.cs at 3376, line 5". About the Layout cycle detected exception, please check if there is such a scenario that leads to permanent re-layout, that might caused this exception.
-
Fay Wang - MSFT • 5,221 Reputation points
2020-05-08T09:15:53.747+00:00 Hi, have you solved your issue? Do you have other questions?
-
Fay Wang - MSFT • 5,221 Reputation points
2020-05-15T09:25:28.807+00:00 Hi, is there any update?
-
MG Bhadurudeen • 631 Reputation points
2020-05-15T16:19:35.32+00:00 Sorry for the late reply.
I was unable to login to this site, it was reloading automatically continuously, disallowing me to do any operation.I test my app in release mode too, I worked without any bug. so I am unable to figure out the area of issue.
-
MG Bhadurudeen • 631 Reputation points
2020-05-15T16:25:42.223+00:00 SharedStubs.g.cs at 3376, line 5" is not my code. It is a file generated by the visual studio.
Here is the code in that file at that line:
global::System.GC.KeepAlive(__this); if (__result < 0) global::McgInterop.McgHelpers.ThrowFailed( __result, __typeHnd ); return __result;
-
MG Bhadurudeen • 631 Reputation points
2020-05-15T16:40:27.68+00:00 please check if there is such a scenario that leads to permanent re-layout
Let me check this again.
-
Fay Wang - MSFT • 5,221 Reputation points
2020-05-19T05:08:27.41+00:00 OK, if there is any progress about leading to permanent re-layout, please update here. And may be you can also check the pages mentioned in the error message to see if there is something wrong.
Sign in to comment