Bug 15598 - iOS SDKs not synching properly
Summary: iOS SDKs not synching properly
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.4.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-10-22 16:58 UTC by Allie Miller
Modified: 2015-08-04 09:42 UTC (History)
5 users (show)

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

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:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Allie Miller 2013-10-22 16:58:41 UTC
Created attachment 5210 [details]
Log from Case #49419

When trying to activate Xamarin.iOS on a Windows workstation, the license file is created on the Windows workstation. However, Visual Studio still says it is a "Starter" version of the software.  

Inside the IDE log files (attached to this bug) the error "System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host" appears.

Xcode is installed at "/Applications"

Updating to the alpha channel did not fix the issue.
Comment 2 Abhishek 2015-07-31 11:49:26 UTC
I have tried this issue with the latest build XVS 3.11.666 and unable to reproduce this issue at our end.

As if now I am closing this issue.Feel free to reopen this issue if it still exist.