api issue

Im getting this error
Supported API test

FAILED
Supported APIs

  • Error Found: The supported APIs test detected the following errors:

  • API DXGIGetDebugInterface1 in dxgi.dll is not supported for this application type. UnityPlayer.dll calls this API.

  • API GetFileVersionInfoSizeA in version.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. See the link below for more information:
    Alternatives to Windows APIs in Microsoft Store apps.

How do i fix this in the simplest form? i dont even know what i did wrong, please help

You need to build your game in “Master” configuration, rather than “Release”.

2 Likes

That’s what I did, I put it in master, do you think it’s because .net native isn’t in the build? Because I put it as a component in visual studio

You don’t need .NET Native.

Can you show screenshots of step by step on how you create the app package?

Yes of course, let me go on my computer

I followed this tutorial, is this correct?
https://www.youtube.com/watch?v=AKCxHDrbiwc

Yes, at 3:55 they set the build configuration to master. Did you do that? Those errors you’re showing come from release builds, so either it’s that or something else is causing the release build to be built.

Yes I did set it to master build, I updated my visual studio today too so I will see if it was a bug later tonight

It worked! It was just a bug in visual studio! Thank you!

just curious what visual studios you upgraded to? I’m using 2019 and getting this same error

I don’t remember what version I was using but I just upgraded to the latest stable version about 2 weeks ago and this issue isn’t happening