New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UWP Cant Submit to store Error API FreeAddrInfoEx #924

Open
liliyashka opened this Issue Nov 16, 2018 · 17 comments

Comments

Projects
None yet
9 participants
@liliyashka
Copy link

liliyashka commented Nov 16, 2018

I have installed the new update from nuget 6.2.2 and I get a certification error when the app is processing. Here is the result.
Supported APIs
Error Found: The supported APIs test detected the following errors:
API FreeAddrInfoEx in ws2_32.dll is not supported for this application type. myApp.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:

@schuettecarsten

This comment has been minimized.

Copy link

schuettecarsten commented Nov 20, 2018

Same problem for our app. Downgrading to v6.1.9 fixes this.

@MichalStrehovsky

This comment has been minimized.

Copy link
Member

MichalStrehovsky commented Nov 21, 2018

Thanks for bringing this to our attention and sorry for the trouble. This seems to be caused by a reference to this API being added in dotnet/corefx#26850. This was subsequently fixed to rely on the supported API in dotnet/corefx#29919 but that change didn't make it to the version of the framework UWP 6.2.2 shipped with. We'll look into addressing this problem.

@liliyashka

This comment has been minimized.

Copy link

liliyashka commented Nov 21, 2018

How long will it take to fix? Thanks.

@martinsuchan

This comment has been minimized.

Copy link

martinsuchan commented Nov 28, 2018

Is there any workaround to fix this issue, like updating specific .NET NuGet dependency? Or should we use Microsoft.NETCore.UniversalWindowsPlatform 6.1.9 before this issue is fixed?
It's also strange that the Windows App Certification Kit 10.0.17763.132 does not show any problem with unsupported API when testing the app locally.

@shaishavbhatt08

This comment has been minimized.

Copy link

shaishavbhatt08 commented Nov 29, 2018

Have the same issue!

@Levvy055

This comment has been minimized.

Copy link

Levvy055 commented Dec 3, 2018

Also the same. And getting it on local cert tool

@shaishavbhatt08

This comment has been minimized.

Copy link

shaishavbhatt08 commented Dec 3, 2018

Use Microsoft.NETCore.UniversalWindowsPlatform 6.1.9, Next release will solve the issue i hope.

@shaishavbhatt08

This comment has been minimized.

Copy link

shaishavbhatt08 commented Dec 3, 2018

I submitted the app with use Microsoft.NETCore.UniversalWindowsPlatform 6.1.9 and it did not fail

@erossetto

This comment has been minimized.

Copy link

erossetto commented Dec 3, 2018

I also had to downgrade... how is the nuget 6.2.2 not fixed or removed yet? This is causing devs to waste hours

@MichalStrehovsky

This comment has been minimized.

Copy link
Member

MichalStrehovsky commented Dec 3, 2018

how is the nuget 6.2.2 not fixed or removed yet?

It was pulled down a couple days ago: 6.1.9 is the latest stable package: https://www.nuget.org/packages/Microsoft.NETCore.UniversalWindowsPlatform

We are working on an update with a fix for this issue.

@LanceMcCarthy

This comment has been minimized.

Copy link

LanceMcCarthy commented Dec 27, 2018

Any update on the progress of this?

@yrest

This comment has been minimized.

Copy link

yrest commented Jan 4, 2019

Automatically updated to 6.2.2 today unaware of the issue, this is ridiculous.

@MichalStrehovsky

This comment has been minimized.

Copy link
Member

MichalStrehovsky commented Jan 4, 2019

@yrest The 6.2.2 package is still unpublished: https://www.nuget.org/packages/Microsoft.NETCore.UniversalWindowsPlatform. You shouldn't be offered to update to 6.2.2.

@LanceMcCarthy

This comment has been minimized.

Copy link

LanceMcCarthy commented Jan 4, 2019

It looks like 6.2.3 is now officially available. @yrest @erossetto @shaishavbhatt08

[edited to remove unlisted cached 6.2.3 version]

@LanceMcCarthy

This comment has been minimized.

Copy link

LanceMcCarthy commented Jan 5, 2019

I just spoke to a few folks, don't use 6.2.3 unless you absolutely need support for ARM64. They still haven't fixed the underlying problem.

#931 (comment)

@yrest

This comment has been minimized.

Copy link

yrest commented Jan 7, 2019

In a sense, all these are good things to learn and try to understand, I appreciate it, but from a user's perspective it's just a waste of time. :]
As soon as I update from 6.2.2 to 6.1.9 am getting weird exceptions, like following...
But when app is packaged using 6.2.2 it is being rejected by the store with subject.

System.MissingMethodException
HResult=0x80131513
Message=Method not found: 'System.ReadOnlySpan`1 System.String.op_Implicit(System.String)'.
Source=System.IO.FileSystem
StackTrace:
at System.IO.PathInternal.TrimEndingDirectorySeparator(String path)
at System.IO.FileSystem.FillAttributeInfo(String path, WIN32_FILE_ATTRIBUTE_DATA& data, Boolean returnErrorOnNotFound)
at System.IO.FileSystem.DirectoryExists(String path, Int32& lastError)
at System.IO.Directory.Exists(String path)
at …

Maybe it's a coincidence, but before I upgraded to 1809 at the end of November, all was good.

@yrest

This comment has been minimized.

Copy link

yrest commented Jan 7, 2019

I must apologise for slightly misleading statements... Have restored back my original project and discovered that it was using 6.2.2 already for a while, meaning Microsoft.NETCore.UniversalWindowsPlatform has not been updated recently for me!
It seems updating Xamarin.Forms to 3.4.0.1009999 causes confusion somewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment