We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.
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.
The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.
On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.
So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. 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. And always feel free to hit us up on Twitter @MxdRealityDev.
Fail to pass certification on UnityPlayer.dll
We are developing Windows Power BI App.
In our recent package, we have added support to Holographic device family.
Unfortunately, during publishing the package to store, it failed to pass the ‘Certification process’.
Name: Microsoft Power BI for Windows
App ID: 9NBLGGGZLXN1
Publisher Name: Microsoft Corporation
Test ID: 6c2d246a-646e-4a9e-aac2-9e7e14e87367
Review Completed: 03/08/2018 16:26
Supported API test
· Error Found: The supported APIs test detected the following errors:
· API D3D12GetDebugInterface in d3d12.dll is not supported for this application type. UnityPlayer.dll calls this API.
· Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
· How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable.
We have tried different solutions that are suggested over the internet but it did not worked for us. (e.g. Build project as master)
Have you any idea why it fails and what we are doing wrong?