Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Windows App Certification Kit (10.0.18362.1) Failed

Discussion in 'Windows' started by hardartcore, Nov 17, 2020.

  1. hardartcore

    hardartcore

    Joined:
    Jan 27, 2017
    Posts:
    43
    Hi,
    I am trying to prepare a package for uploading to Microsoft Store, but currently have issues with the Certification Kit. Those are by build settings from inside Unity:


    And when tried to validate the generated package via Visual Studio and Windows App Certification Kit I get this errors:

    Windows security features test
    FAILED
    Binary analyzer
    • Error Found: The binary analyzer test detected the following errors:
      • File ProResToolbox.dll has failed the AppContainerCheck check.
      • File ProResWrapper.dll has failed the AppContainerCheck check.
    • Impact if not fixed: If the app doesn’t use the available Windows protections, it can increase the vulnerability of the customer's computer to malware.
    • How to fix: Apply the required linker options - SAFESEH, DYNAMICBASE, NXCOMPAT, and APPCONTAINER - when you link the app. See links below for more information:



    And

    Supported API test

    FAILED
    Supported APIs
    • Error Found: The supported APIs test detected the following errors:
      • API _CxxThrowException in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API __C_specific_handler in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API __CxxFrameHandler3 in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API __std_exception_copy in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API __std_exception_destroy in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API __std_terminate in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API __std_type_info_destroy_list in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API memcpy in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API memmove in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API memset in vcruntime140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ??6?$basic_ostream@DU?$char_traits@D@std@@@std@@QEAAAEAV01@H@Z in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ?_Osfx@?$basic_ostream@DU?$char_traits@D@std@@@std@@QEAAXXZ in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ?_Xlength_error@std@@YAXPEBD@Z in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ?cerr@std@@3V?$basic_ostream@DU?$char_traits@D@std@@@1@A in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ?cout@std@@3V?$basic_ostream@DU?$char_traits@D@std@@@1@A in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ?flush@?$basic_ostream@DU?$char_traits@D@std@@@std@@QEAAAEAV12@XZ in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ?setstate@?$basic_ios@DU?$char_traits@D@std@@@std@@QEAAXH_N@Z in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ?sputc@?$basic_streambuf@DU?$char_traits@D@std@@@std@@QEAAHD@Z in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ?sputn@?$basic_streambuf@DU?$char_traits@D@std@@@std@@QEAA_JPEBD_J@Z in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API ?uncaught_exception@std@@YA_NXZ in msvcp140.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API wsprintfW in user32.dll is not supported for this application type. ProResWrapper.dll calls this API.
      • API __CxxFrameHandler4 in vcruntime140_1_app.dll is not supported for this application type. GameAssembly.dll calls this API.
      • API __C_specific_handler in vcruntime140.dll is not supported for this application type. ProResToolbox.dll calls this API.
      • API __std_type_info_destroy_list in vcruntime140.dll is not supported for this application type. ProResToolbox.dll calls this API.
      • API memcmp in vcruntime140.dll is not supported for this application type. ProResToolbox.dll calls this API.
      • API memcpy in vcruntime140.dll is not supported for this application type. ProResToolbox.dll calls this API.
      • API memmove in vcruntime140.dll is not supported for this application type. ProResToolbox.dll calls this API.
      • API memset in vcruntime140.dll is not supported for this application type. ProResToolbox.dll calls this API.
      • API __CxxFrameHandler4 in vcruntime140_1_app.dll is not supported for this application type. Commandos Mission.exe 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:



    And last but not least I am using Scripting Backend: IL2CPP, .NET 4.x and Master build.
     
  2. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,504
    This one can be ignored. See https://developercommunity.visualst...63-runtime-uses-an-unsupported-api-for-u.html

    The rest, however, are real issues. They are caused by a known issue in Unity recorder package. There's a bug in the plugin configuration that causes those DLLs be included in the build. A fix is in progress, but you should be able to work around it by deleting them from generated visual studio project folder before building an app package for the store.
     
    hardartcore likes this.
  3. hardartcore

    hardartcore

    Joined:
    Jan 27, 2017
    Posts:
    43
    Hi,
    Thanks a lot for the reply! Removing Unity Recorder package actually fixes the issues with failing Certification Kit.