UWP application - WACK failure

[andrewdewaal]

Hello,

We have a UWP application using the libsodium NuGet package.

We are using this package to verify cryptographic signatures, as we've been unable to find a package that wrapped all the functions we need in libsodium. We reference this package directly, and have a wrapper on top to call the needed methods from the DLL.

This functions as expected, and all works very well.

However, when the Windows App Certification Kit is run, we get the following error:
API __C_specific_handler in vcruntime140.dll is not supported for this application type. libsodium.dll calls this API.
API __std_type_info_destroy_list in vcruntime140.dll is not supported for this application type. libsodium.dll calls this API.
API memcpy in vcruntime140.dll is not supported for this application type. libsodium.dll calls this API.
API memmove in vcruntime140.dll is not supported for this application type. libsodium.dll calls this API.
API memset in vcruntime140.dll is not supported for this application type. libsodium.dll calls this API.
API strchr in vcruntime140.dll is not supported for this application type. libsodium.dll calls this API.
API strrchr in vcruntime140.dll is not supported for this application type. libsodium.dll calls this API.

It turns out this has been failing since bringing in libsodium, but only now is Microsoft rejecting App Store submissions failing on this part of the certification.

We do have references to Visual C++ 2015 Runtime for Universal Windows Platform Apps and Visual C++ 2015 UWP Desktop Runtime for native apps in our UWP project which references the project containing the libsodium methods.

This matches the answers provided in these (possibly) related issues:
ektrah/libsodium-core#66
https://developercommunity.visualstudio.com/t/vcruntime140dll-is-missing-on-uwp-xbox/1073368#T-N1082473

Are there any suggestion on what could be done to resolve this?

Thanks very much!