App Certificaion fails with: API FreeAddrInfoEx in ws2_32.dll is not supported for this application type
up vote
0
down vote
favorite
I created a very simple Xamarin Forms App which uses ZXing.Net.Mobile and HttpClient (the app scans a bar-/QR-code and sends it to a server). This app was successfully released in the App Store and the Play Store, but when uploading it to the Microsoft Store the Certification fails with the following message on each architecture (x86, x64, ARM, ARM64) in the "Supported API test" section:
API FreeAddrInfoEx in ws2_32.dll is not supported for this application type. MyApp.UWP.dll calls this API.
I do not know what causes this, but I suspect ZXing as this is the only third-Party library I did not use in a published app before.
Does anybody know how I can solve this?
xamarin xamarin.forms uwp windows-store zxing.net
asked Nov 17 at 10:41
ChrFin
17.5k75291
add a comment |
up vote
0
down vote
favorite
I created a very simple Xamarin Forms App which uses ZXing.Net.Mobile and HttpClient (the app scans a bar-/QR-code and sends it to a server). This app was successfully released in the App Store and the Play Store, but when uploading it to the Microsoft Store the Certification fails with the following message on each architecture (x86, x64, ARM, ARM64) in the "Supported API test" section:
API FreeAddrInfoEx in ws2_32.dll is not supported for this application type. MyApp.UWP.dll calls this API.
I do not know what causes this, but I suspect ZXing as this is the only third-Party library I did not use in a published app before.
Does anybody know how I can solve this?
xamarin xamarin.forms uwp windows-store zxing.net
asked Nov 17 at 10:41
ChrFin
17.5k75291
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I created a very simple Xamarin Forms App which uses ZXing.Net.Mobile and HttpClient (the app scans a bar-/QR-code and sends it to a server). This app was successfully released in the App Store and the Play Store, but when uploading it to the Microsoft Store the Certification fails with the following message on each architecture (x86, x64, ARM, ARM64) in the "Supported API test" section:
API FreeAddrInfoEx in ws2_32.dll is not supported for this application type. MyApp.UWP.dll calls this API.
I do not know what causes this, but I suspect ZXing as this is the only third-Party library I did not use in a published app before.
Does anybody know how I can solve this?
xamarin xamarin.forms uwp windows-store zxing.net
asked Nov 17 at 10:41
ChrFin
17.5k75291
I created a very simple Xamarin Forms App which uses ZXing.Net.Mobile and HttpClient (the app scans a bar-/QR-code and sends it to a server). This app was successfully released in the App Store and the Play Store, but when uploading it to the Microsoft Store the Certification fails with the following message on each architecture (x86, x64, ARM, ARM64) in the "Supported API test" section:
API FreeAddrInfoEx in ws2_32.dll is not supported for this application type. MyApp.UWP.dll calls this API.
I do not know what causes this, but I suspect ZXing as this is the only third-Party library I did not use in a published app before.
Does anybody know how I can solve this?
xamarin xamarin.forms uwp windows-store zxing.net
xamarin xamarin.forms uwp windows-store zxing.net
asked Nov 17 at 10:41
ChrFin
17.5k75291
asked Nov 17 at 10:41
ChrFin
17.5k75291
asked Nov 17 at 10:41
ChrFin
17.5k75291
asked Nov 17 at 10:41
ChrFin
17.5k75291
asked Nov 17 at 10:41
ChrFin
17.5k75291
17.5k75291
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Derive from the blog:
When you run the WACK on a UWP app that did not go through this compilation process, you will get a not-so-trivial failure. It will look something like:
API ExecuteAssembly in uwphost.dll is not supported for this application type. App.exe calls this API.
.......
The fix is to make sure you are creating your packages properly, and running WACK on the right one. If you follow these packaging guidelines, you should never encounter this issue.
Please pay attention the part:Before packaging your app and check your app as required.
answered 2 days ago
DasiyTian MSFT
1045
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Derive from the blog:
When you run the WACK on a UWP app that did not go through this compilation process, you will get a not-so-trivial failure. It will look something like:
API ExecuteAssembly in uwphost.dll is not supported for this application type. App.exe calls this API.
.......
The fix is to make sure you are creating your packages properly, and running WACK on the right one. If you follow these packaging guidelines, you should never encounter this issue.
Please pay attention the part:Before packaging your app and check your app as required.
answered 2 days ago
DasiyTian MSFT
1045
add a comment |
up vote
0
down vote
Derive from the blog:
When you run the WACK on a UWP app that did not go through this compilation process, you will get a not-so-trivial failure. It will look something like:
API ExecuteAssembly in uwphost.dll is not supported for this application type. App.exe calls this API.
.......
The fix is to make sure you are creating your packages properly, and running WACK on the right one. If you follow these packaging guidelines, you should never encounter this issue.
Please pay attention the part:Before packaging your app and check your app as required.
answered 2 days ago
DasiyTian MSFT
1045
add a comment |
up vote
0
down vote
up vote
0
down vote
Derive from the blog:
When you run the WACK on a UWP app that did not go through this compilation process, you will get a not-so-trivial failure. It will look something like:
API ExecuteAssembly in uwphost.dll is not supported for this application type. App.exe calls this API.
.......
The fix is to make sure you are creating your packages properly, and running WACK on the right one. If you follow these packaging guidelines, you should never encounter this issue.
Please pay attention the part:Before packaging your app and check your app as required.
answered 2 days ago
DasiyTian MSFT
1045
Derive from the blog:
When you run the WACK on a UWP app that did not go through this compilation process, you will get a not-so-trivial failure. It will look something like:
API ExecuteAssembly in uwphost.dll is not supported for this application type. App.exe calls this API.
.......
The fix is to make sure you are creating your packages properly, and running WACK on the right one. If you follow these packaging guidelines, you should never encounter this issue.
Please pay attention the part:Before packaging your app and check your app as required.
answered 2 days ago
DasiyTian MSFT
1045
answered 2 days ago
DasiyTian MSFT
1045
answered 2 days ago
DasiyTian MSFT
1045
answered 2 days ago
DasiyTian MSFT
1045
1045
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53350429%2fapp-certificaion-fails-with-api-freeaddrinfoex-in-ws2-32-dll-is-not-supported-f%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
