The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Publishing to store issue, app cert kit fails
App runs fine on device, compiles without error, but when I run the app certification kit test for the store it fails under "supported APIs" throwing the following errors:
API D3D12GetDebugInterface in d3d12.dll is not supported for this application type. UnityPlayer.dll calls this API.
API DeregisterEventSource in advapi32.dll is not supported for this application type. AudioIO2.dll calls this API.
API RegisterEventSourceW in advapi32.dll is not supported for this application type. AudioIO2.dll calls this API.
API ReportEventW in advapi32.dll is not supported for this application type. AudioIO2.dll calls this API.
API ExecuteAssembly in uwphost.dll is not supported for this application type. HoloHack.exe calls this API.
API DllGetActivationFactory in uwphost.dll is not supported for this application type. HoloHack.exe has an export that forwards to this API.
API OpenSemaphore in api-ms-win-core-synch-l1-1-0.dll is not supported for this application type. System.Threading.dll calls this API.
API CreateSemaphore in api-ms-win-core-kernel32-legacy-l1-1-0.dll is not supported for this application type. System.Threading.dll calls this API.
Building for release, x86, and using the latest 5.4.0f1-HTP unity version although the I was having the same problem with previous version which is why I updated...
Any ideas?
Best Answer
-
Options
spt
✭✭
You have to use the "Master" configuration, not the "Release" or "Debug".
This is apparently a configuration custom created by Unity which removes all profiling and debugging references.5
Answers
You have to use the "Master" configuration, not the "Release" or "Debug".
This is apparently a configuration custom created by Unity which removes all profiling and debugging references.