Sunday, October 27, 2013

Unity - Failing Store Submission or WACK with Windows 8 Games

I was helping a developer in porting their game to work on Windows 8. They had done the export in Unity (Build Settings - Windows Store Apps, as shown below) and uploaded the package to the Windows Store.

So far, pretty easy and straightforward process. The store review process rejected the application. I asked the to run WACK locally (Windows Application Certification Kit) that is on any system that is doing Windows 8 development. To run it, simply hit the windows key on your keyboard and type cert, it should be in the results. It's also available at

WACK failed and gave the following issues in the report. I'm including everything for those that find this via a search engine trying to solve their own issues. However the fix was quite simple. In Visual Studio ensure you are doing a RELEASE build. The problem here is when a Debug build is selected in Visual Studio, the debug version of the Unity libraries are referenced instead of the Release version. Debug libraries have optimizations removed and a bunch of diagnostic information included in them (for ex information to link in PDB files for debug information). Simply select "Release" in Visual Studio for build settings, recompile via the build menu or control-shift-b, which is also the same hotkey for build in Unity and voila!

Failing application details:
Binary analyzer
Error Found: The binary analyzer test detected the following errors:
File \AppX\BridgeInterface.dll has failed the WXCheck check.
File \AppX\BridgeInterface.dll has failed the SafeSEHCheck check.
File \AppX\Catch Falling Stuff.exe has failed the WXCheck check.
File \AppX\Catch Falling Stuff.exe has failed the SafeSEHCheck check.
File \AppX\UnityEngineDelegates.dll has failed the WXCheck check.
File \AppX\UnityEngineDelegates.dll has failed the SafeSEHCheck check.

Impact if not fixed: If the app doesn’t use the available Windows protections, it can increase the vulnerability of customer's computer to malware.

How to fix: Apply the required linker options - SAFESEH, DYNAMICBASE, NXCOMPAT, and APPCONTAINER - when you link the app. See links below for more information:
Fixing Binary Analyzer Errors

Debug configuration
Error Found: The debug configuration test detected the following errors: ?The binary UnityPlayer.dll is built in debug mode.
The binary BridgeInterface.dll is built in debug mode.
The binary UnityEngineProxy.dll is built in debug mode.
The binary UnityEngineDelegates.dll is built in debug mode.
The binary Catch Falling Stuff.exe is built in debug mode.
This package has a dependency on Microsoft.VCLibs.110.00.Debug.
Impact if not fixed:  Windows Store doesn’t allow a debug version of an app.
How to fix:  Please make sure the app isn’t linking to any debug versions of a framework, and it is built with release configuration. If this is a managed app please make sure you have installed the correct version of .NET framework.


  1. Build Settings - Windows Store is a great application for users. I'm working with .net development company for business software, namely development of complex web systems based on ASP.NET / MVC. And with Windows Azure application.

  2. Good Article,Get your website up and running right away by choosing one of the existing designs.Massage Perfect
    Websites do the work for you! massage websites come with a library of content written by massage professionals.
    massage websites

  3. Top web developemnt, web designing and web hosting company in

    the world. That developed wordpress themes and all other CMS

    themes and provide free webhosting and paid web hosting for your

  4. The other way to business Forex dealing is to study the marketplace, discover all the relevant essential details, take MockingBird Method Softwarequite a a lengthy time duration of a few months to a very extensive period to understand something,

  5. Hello, I have browsed most of your posts.

  6. On top of this, it can also end up using a lot of memory because it must file formal reports regarding the errors encountered by your system. Windows error

  7. On the off chance that you've come to this far and still don't have a working printer, the odds are that your printer has achieved the end of its valuable life -- with Windows 10, at any rate.

  8. This comment has been removed by the author.


Note: Only a member of this blog may post a comment.