none
[UWP][C#] My app is unhealthy RRS feed

  • Question

  • Hi.

    I have a UWP app published to the Store and works great. The latest version I submitted to the store worked fine in Debug and Release builds locally, it passes the Windows App Cert Kit tests, it passes the Store certification process but it crash at runtime when I (or everyone else) download it from the store. The Store's Health report gives me a useless (at least for me) stack trace. What I did to fix the issue was to submit a previous version and guess what... same errors, that submit was the previous, working version (from a source control). Here is the stack trace from the Health report. Please, any help will be welcomed, I'm desperate:

    Frame Image Function Offset 0 KERNELBASE.dll RaiseFailFastException 0x0000000000000074
    1 mrt100_app.dll System::Runtime::EH.GetRuntimeException 0x0000000000000014
    2 mrt100_app.dll System::Runtime::EH.GetClasslibException 0x0000000000000045
    3 mrt100_app.dll System::Runtime::EH.RhThrowHwEx 0x0000000000000063
    4 mrt100_app.dll RhpThrowHwEx2 0x0000000000000000
    5 mrt100_app.dll System::Runtime::TypeCast.AreTypesEquivalentInternal 0x0000000000000071
    6 mrt100_app.dll System::Runtime::TypeCast.AreTypesEquivalent 0x0000000000000009
    7 null Internal::Runtime::TypeLoader::RuntimeTypeHandleEqualityComparer.Equals 0x0000000000000047
    8 null System::Collections::Generic::Internal::Dictionary$2_System::RuntimeTypeHandle,System::Int32_.FindEntry 0x0000000000000096
    9 null System::Collections::Generic::Internal::Dictionary$2_System::RuntimeTypeHandle,System::Int32_.TryGetValue 0x0000000000000011
    10 null System::Runtime::InteropServices::McgModuleManager.InsertDataIntoDictionary 0x0000000000000089
    11 null System::Runtime::InteropServices::McgModuleManager.Initialize 0x0000000000000240
    12 myapp.mcginterop.dll Mcg::StartupCodeTrigger.Initialize 0x0000000000000038
    13 myapp.exe $ILCT$::$ILT$MainMethodType$.NewMainMethod 0x000000000000000B
    14 myapp.dll RHBinder__ManagedInitAndLaunch 0x0000000000000020
    15 myapp.dll RHBinder__ShimExeMain 0x000000000000000D
    16 kernel32.dll BaseThreadInitThunk 0x0000000000000014
    17 ntdll.dll RtlUserThreadStart 0x0000000000000021

    Wednesday, June 6, 2018 6:30 AM

All replies

  • Hi ,

    This problem is strange and it is not suitable to discuss via the forum. It needs more professional support. I suggest that you might need to open a support ticket for this. Please contact our paid phone support at MS Support. You will get 1:1 support on that. Please kindly note that your support ticket will be free if it is Microsoft's issue.

    Best regards,

    Roy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, June 7, 2018 2:11 AM
  • Hi Roy.

    I did opened a ticket and this was the answer

    I did understand that your app was seeing more crashes since your last update and you reverted back to the previous build, but you are still seeing crashes. I have reviewed your health report and it shows that the crashes actually went up from 2 submissions ago.  Before that the crashes were low.

    This issue surpasses our support and would suggest to post your question on the Tech Forums to get advice from one of our technical advisors.

    I´m really frustrated at this point.

    Thursday, June 7, 2018 7:14 PM
  • Hi Leisvan Cordero,
    Sorry for the delay.
    Which kind ticket did you create? Did you create the free ticket from the Dev Center?
    This problem is out of the scope for Dev Center. You need to create a paid development ticket with the link I posted in my last reply.

    Best regards,
    Roy

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, June 13, 2018 7:34 AM
  • Hi Roy. Thanks again. I'm on it.
    Wednesday, June 13, 2018 7:55 AM