none
Windows App Certification FAILED cannot launch myApp RRS feed

  • Question

  • In Visual Studio Community 2015 I do Project > Store > Create App Packages, and all goes well, but when I run the WACK it fails with

    Cannot launch myAppName

    Any ideas on what I need to do to get the app to pass the test?

    All the other tests pass.  The app runs fine with the same settings. 

    I increment the version number every time I run or test the app.

    The build settings are Release/ Windows-x86/ Local Machine

    My local machine is Microsoft Windows 10 Home (10.0.10586.0)

    I have looked for the solution in this forum post:  FileStream.Open which was not specified with access flags, but I did not have a case of that in my code.

    And I have also reviewed my app for the issue found in this forum post: Not running on a 64 bit machine. but that was fine.

    Here is the text of the test results:

    Windows App Certification Kit - Test Results

    App name:
    myAppName
    App publisher:
    pdschullerDotCom LLC
    App version:
    2.1.0.9
    OS Version:
    Microsoft Windows 10 Home (10.0.10586.0)
    Kit Version:
    10.0
    Architecture:
    x64
    Report time:
    7/21/2016 9:05:22 PM


    Overall result: FAILED



    Deployment and launch tests
    PASSED
    Bytecode generation
    FAILED
    App launch
        • Error Found: The app launch test detected the following errors:
          • Cannot launch pdsKcGrt
        • Cannot launch pdsKcGrt

    • Edited by pdschuller_ Thursday, August 4, 2016 11:58 PM Edited Aug 4 2016
    Friday, July 22, 2016 1:30 AM

All replies

  • Here are some steps that you can follow for this and other WACK errors and WACK test FAILED

    1. Start the WACK process from Visual Studio (I am using VS Community 2015)
      For me I do Project > Store > Create App Packages > Yes
    2. Before starting the WACK process attach to that process.
      After the system builds you package, THEN you will be asked to start the WACK process.  Launch it then attach to it.
      I did Debug > Attach To Process
      NOTE: I installed Windows Driver Kit (WDK) first. Debugging Tools for Windows is included in the WDK. I am not sure if I really had to do that.

    3. The debugger will stop the WACK process when the exception is hit.  Just continue with OK's.  What you need has already been generated.

    4. The error report you want is a .wer file it is at C:\ProgramData\Microsoft\Windows\WER\ReportArchive
      You'll see the folder the process just created there by date.

    5. Open Report.wer in NotePad.  This report should tell you the line of code that crashed WACK.
      Mine has this in it (this is for the issue I worked on the other day. Not the issue in the above post).
      Sig[1].Value=io.cordova.myappae40f8
      Sig[2].Name=RestrictedStackHash
      Sig[2].Value=e486
      Sig[3].Name=ExceptionType
      Sig[3].Value=3
      Sig[4].Name=Filename
      Sig[4].Value=ms-appx:////48622ecfe83d7.kcdapemawindowstablet//www//js//core//appcontext.js
      Sig[5].Name=SourcePosition
      Sig[5].Value=182_15
    6. The error was on line 182 of appcontext.js

    Phil

    Friday, October 14, 2016 2:34 PM