Bug 56615 - Failed to resolve IMonoSslStream::AuthenticateAsClient
Summary: Failed to resolve IMonoSslStream::AuthenticateAsClient
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: unspecified
Hardware: PC Windows
: Normal normal
Target Milestone: 15.4
Assignee: Bugzilla
Depends on:
Reported: 2017-05-18 13:19 UTC by Hakan KIRIK
Modified: 2017-07-19 21:18 UTC (History)
9 users (show)

Is this bug a regression?: ---
Last known good build:

Build Output (79.96 KB, text/plain)
2017-05-22 10:56 UTC, Hakan KIRIK

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Hakan KIRIK 2017-05-18 13:19:02 UTC
Xamarin.IOS Project builds on Mac without error. Same codes gives error like this:

Failed to resolve "System.Void Mono.Security.Interface.IMonoSslStream::AuthenticateAsClient(System.String)" reference from "Mono.Security, Version=, Culture=neutral, PublicKeyToken=0738eb9f132ed756"

Both on VS Community 2017 and Xamarin.IOS (Windows) and (Mac)
It worked before upgrading to 10.10 on Windows too.
Comment 1 Hakan KIRIK 2017-05-18 13:21:59 UTC
error only on Windows
Comment 2 Vincent Dondain [MSFT] 2017-05-18 13:40:04 UTC
Please include your full build logs, crash reports (if any), test case (to reproduce) and all version informations.

To get full build logs just set the log verbosity to diagnostic at the following locations:
- On Visual Studio for Mac: Preferences > Projects > Build
- On Visual Studio for Windows: Tools > Options > Projects and Solutions > Build and Run

On Visual Studio Windows you also want to add `-v -v -v -v` to the mtouch additional arguments by right-clicking the project in the solution explorer and selecting `Properties`.
Note: this is done automatically on Visual Studio for Mac when the log verbosity is set to diagnostic.

The easiest way to get exact version information is to use the "Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details" button and copy/paste the version informations (you can use the "Copy Information" button).
Comment 3 Jose Gallardo 2017-05-18 16:50:34 UTC
Can you please provide the full diagnostic build output from Visual Studio?

Go to the menu "Tools - Options" and from the left panel: "Projects And Solutions - Build And Run" and change "MSBuild Output Verbosity" to "Diagnostic", and then build the solution. Copy the Build Output from the Output window and share it (maybe in a gist or as a zip file).

Comment 4 Hakan KIRIK 2017-05-22 10:56:26 UTC
Created attachment 22345 [details]
Build Output

compressed with Rar
Comment 5 Adrian Alonso 2017-06-21 19:11:10 UTC
Thanks for the logs. We will investigate it.
Comment 6 Emanuel 2017-07-19 21:18:18 UTC
Hi Hakan,
I took a look to the logs you've attached and found an old bug in it, it's VS is using a wrong path for the Mono.Security.dll reference. This issue is fixed in the latest stable release (XVS 

I'm closing this issue as not reproducible. If you're stable able to reproduce this issue using the mentioned version, please try the following:
- Remove the reference to Mono.Security and add it again via "Add Reference -> Assemblies -> Framework -> Mono.Security"
- Make sure the reference was added to the csproj like this: <Reference Include="Mono.Security" />

If you continue hitting this issue after following the mentioned steps feel free to reopen this bug and please attach a new detailed build output and the Visual Studio environment info (Help -> About Microsoft Visual Studio -> Copy Info).

Thanks for reporting!