locked
Windows Store App Ceritfication failed because of unreproducable crashes

    Question

  • Hello,

    our app was rejected by the store's certification process twice because of app crashes after app start. Unfortunately it is not reproducable at all on our tablet devices (mixed architectures) and on several desktop computers including simulators. Uninstalling, launching with new user account and the windows certification kit did not produce any crash or error. We also tried setting up a clean install of Windows on a VM and several app installations on the clean install snapshot did not lead to a reproducable crash.

    Notes of the testers:

    Unfortunately, when our reviewers tried to launch your app failed to launch every time. Our reviewers were unable to complete a review. If we were able to capture a crash report, we have provided it to you.

    The .wer-file we've got from the certification tester contains the following information.

    Sig[1].Name=Application Name
    Sig[1].Value=praid:App
    Sig[2].Name=Application Version
    Sig[2].Value=1.1.0.0
    Sig[3].Name=Application Timestamp
    Sig[3].Value=5409c1e8
    Sig[4].Name=Fault Module Name
    Sig[4].Value=StackHash12_da6
    Sig[5].Name=Fault Module Version
    Sig[5].Value=0.0.0.0
    Sig[6].Name=Fault Module Timestamp
    Sig[6].Value=00000000
    Sig[7].Name=Exception Code
    Sig[7].Value=80070057
    Sig[8].Name=Exception Offset
    Sig[8].Value=0
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.3.9600.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=9687
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=9687254c3d0e3d586a5df65b77fcd485
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=67ec
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=67ec5a17d62886f7fe64a9708eb4101d

    According to this article a stackhash error is related to Data Execution Prevention:

    http://social.technet.microsoft.com/Forums/windows/en-US/3932e3eb-c034-4eb7-aa06-4a0a8e6ea493/fault-module-namestackhash0a9e

    We are using Bugsense for crash reporting and the interesting part is that there is no report available for this crash. So it seems like it is not an unhandled exception.

    Is there anything we can do to fix this crash in our app? Were there any similiar issues in the past?

    Regards

    Sascha Leier

    Wednesday, September 10, 2014 11:37 AM

All replies

  • You did not get a dump because of Bugsense?

    Can you remove that component and submit the app again?  That should give you a dump that you can analyze.


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Thursday, September 11, 2014 12:12 PM
    Moderator
  • So i removed bugsense completely from the project and i didn't get a dump.

    But now the .wer-file shows a little bit more information than before.

    Sig[1].Name=Application Name
    Sig[1].Value=praid:App
    Sig[2].Name=Application Version
    Sig[2].Value=1.1.0.0
    Sig[3].Name=Application Timestamp
    Sig[3].Value=5411bdf2
    Sig[4].Name=Fault Module Name
    Sig[4].Value=combase.dll
    Sig[5].Name=Fault Module Version
    Sig[5].Value=6.3.9600.17031
    Sig[6].Name=Fault Module Timestamp
    Sig[6].Value=53086d7c
    Sig[7].Name=Exception Code
    Sig[7].Value=80070057
    Sig[8].Name=Exception Offset
    Sig[8].Value=00053bff
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.3.9600.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=9687
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=9687254c3d0e3d586a5df65b77fcd485
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=67ec
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=67ec5a17d62886f7fe64a9708eb4101d

    But still it doesn't help me enough to find the problem in our app.

    Regards

    Sascha Leier

    Friday, September 12, 2014 12:38 PM
  • I think at this point you would be best served by opening a support case.


    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Friday, September 12, 2014 12:40 PM
    Moderator