Microsoft Partner Center
A Microsoft website for partners that provides access to product support, a partner community, and other partner services.
876 questions
Windows App Certification Kit fails online test, but succeeds locally
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 78%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Sjors Miltenburg
6
Reputation points
I'm trying to publish an update to my Xamarin.Forms.UWP app in the Windows store.
I publish the app from Visual Studio 2022 Version 17.2.0.
I run the Windows App Certification Kit (v10.0.22000.194) locally, and it passes all tests.
I manually uploaded the .msixupload file and release the new version of my app, but there, during online validation it fails the WACK with the following errors under "supported API test".
API _CxxThrowException in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API __C_specific_handler in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API __std_exception_copy in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API __std_exception_destroy in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API __std_terminate in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API __std_type_info_destroy_list in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API _purecall in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API memcpy in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API memmove in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API memset in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API wcsrchr in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API ?_Xlength_error@std@@YAXPEBD@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API ?_Xout_of_range@std@@YAXPEBD@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API ?__ExceptionPtrAssign@@YAXPEAXPEBX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API ?__ExceptionPtrCopy@@YAXPEAXPEBX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API ?__ExceptionPtrCopyException@@YAXPEAXPEBX1@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API ?__ExceptionPtrCreate@@YAXPEAX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API ?__ExceptionPtrCurrentException@@YAXPEAX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API ?__ExceptionPtrDestroy@@YAXPEAX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API ?__ExceptionPtrRethrow@@YAXPEBX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API. API __CxxFrameHandler4 in vcruntime140_1.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
I find it very strange that my local WACK test succeeds but the online WACK test does not succeed.
Furthermore I find these errors strange, because my app does not reference Microsoft.Web.WebView2.Core.dll so I do not know how to correct this.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 92%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERL%3C/text%3E%3C/svg%3E)
Roy Li - MSFT 31,826 Reputation points Microsoft Vendor2022-05-20T02:24:16.277+00:00 First of all, please take the online WACK as standard. Could you please double check what have you done when you update your app?
-
Sjors Miltenburg 6 Reputation points
2022-05-23T19:04:44.13+00:00 Strange stuff... today I looked at my solution again and noticed this entry 'Microsoft.Web.WebView2.Core.winmd' in my UWP project references.
I could swear it was not there before, as I looked at my references and nuget packages in detail in order to diagnose the problem.
I definitely didn't add this reference by hand.Strangely enough, when I remove the reference, git does not pick up on a change in the .csproj or any other file. I am able to remove it from the ui, but when I close and re-open the solution the reference is there again.
Also I checked out the version that was previously approved (and now in the store) and then the solution also opens with this reference in the uwp project.
I strongly suspect it has something to do with the fact that I recently upgraded the windows SDK version in order to combat yet another problem related to WACK.
I also checked on VS2019, and on an other pc (where I also upgraded the win sdk), but the same behavior there.
I created a fresh XF project, but did not find VS added a reference there.
I don't know how to examine where this reference comes from or how it's added.
-
Roy Li - MSFT 31,826 Reputation points Microsoft Vendor
2022-05-26T06:44:17.553+00:00 That's interesting. Are you using winui controls in your project? If the winui NuGet package is not the reason, could you please try to add the NuGet package one by one to see which is the one that automatically?
Sign in to comment