Recently, I am trying to send my app to Windows Store as x86 and ARM structure. Each time that I sent the application to Windows Store, ARM is passing the Technical compliance test. However, x86 is failing this test.
Each of my apps are compiled in release profile and when I am running my tests for my x86 application, it is passing the WACK 3.0 test.
My application type is C# Direct-X 11 as I have chosen from Unity 3d.
Am I doing something wrong? Before I could send another application but since WACK 3.0 came, I couldn’t send any application to Windows Store from Unity 3d as x86.
I sent an e-mail to Microsoft. None of those links are helpful. If they send me the result from their server, I can share. I am not sure but this might be a bug. Whatever I tried, it is not working…
Unfortunately, msdn forums are not also working. I heard that Microsoft is updating their forum services. When I click the link, it is giving me this error:
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
Hi Guys,
I’ve also got the same problem. Locally both WACK3.0 and the RT version of the test pass, so I have no idea why it fails the automated WACK on MS side. I also get the exact same cert failure report sent to me with no details on what I can do to solve the problem. I’m going to try to get hold of the local MS guys to find out what this is about.
Hey guys!
We got same problem.
We’re keeping contact with MS on this issue too.
Looks like there is some issue that is supposed to be resolved on their side.
A friend of mine failed cert with this issue as well. Support told him to rerun WACK locally, he responded that he did and it passes locally, and we’re still waiting on a response.
I’m surprised and disappointed they make people jump through hoops to diagnose technical failures, rather than just providing the output from the report.
Guys, how did you get WACK 3.0? Did you installed Windows SDK 8.1 or Visual Studio 2013?
Or may be there is some other way to install WACK 3.0 without all the mentioned above?
I suspect that my problem appears because I got WACK 2.2 locally even though I got the latest VS 2012 update, and the remote WACK is 3.0 (it contains several new tests that might be failing in my case).
We have the same issue. Our app is passing WACK 2.2 and 3.x on local computers. The xapp has been scanned for malware from multiple computers, and has been rebuilt on completely different computers just to see if it has been an effect. We have tried to get it out 10 times tyring everything (like recoding all js scripts to c#, submit from different computers and so on).
Anyone heard any updates regarding this issue?
Our game is really simple and almost no assets from asset store has been used - just to try and publish a “pure built-in unity” game.
We’re facing a similar issue just trying to submit an update to our game. Passes WACK 3.0 and 2.2, run on x86 and ARM. All previous updates have gone through without issue.
Opened a ticket with Microsoft yesterday and waiting on a response.
Same issue with me! Passes on my local PC but fails when uploaded to the store. This has happened since about a week ago. Before that my other apps always passed when uploaded. Now even though it passes on my local PC it fails when I upload it the same as above!
I am using Unity 4.2.0. I rolled back from Unity 4.2.1 because I thought it might just be a problem with 4.2.1 but no.
PS. I am using Windows 8.0. I wonder if the problem will go away when we all update to Windows 8.1 in October 18th? Perhaps Unity is not compatible with Windows 8.1?
The apps pass both WACK 2.2 and WACK 3.0 no problem on my PC.
Maybe someone at Unity contact someone at Microsoft and sort out the problem? (especially since that Unity Windows 8 App competition ends in two days!)
What is weird is here is the screenshot just before it failed:
