Hey guys, looks like Microsoft broke something with their new dashboard,
So let’s start with this: WinPhone 8.1 Certification Failure - Unity Engine - Unity Discussions
This was an old problem someone found where a bug in the WACK was causing Windows Phone certification failure due to UnityEngineProxy.dll. The solution was that that bug would not prevent submission to Windows Store, and that it should be ignored.
Now, the future is here, and I’m doing a local WACK test on my project using Unity 4.6.6p4 and it passes WACK! Yay. However, it fails submission to the app store because of the exact same reason previous people had their LOCAL tests fail, and I don’t seem to be the only person with this problem: https://social.msdn.microsoft.com/Forums/en-US/8f4515c9-77ca-4c1d-8d02-9db065add540/wack-test-passed-locally-but-failed-after-submission?forum=wpdevelop
This issue that was previously ignorable seems to be now causing critical failures after the introduction of the new Windows Store dashboard that came out within the last day or so. I’m going to try resubmitting my app, but this issue is definitely a problem I thought you guys should know about. I have the latest WACK, the latest Visual Studio 2013, and multiple people have reported this issue in both Unity 4.6.7 and in Unity 5.1
I somehow doubt it’s a Unity problem, it looks more like Microsoft changed a bunch of stuff, but I figured people should know about it.