Bug 42346 - Xamarin iOS DocSync updates daily
Summary: Xamarin iOS DocSync updates daily
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-07-04 16:12 UTC by Reader Man
Modified: 2016-12-23 02:52 UTC (History)
7 users (show)

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

Xamarin iOS DocSync updates daily (14.57 KB, image/png)
2016-07-04 16:12 UTC, Reader Man

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 Reader Man 2016-07-04 16:12:15 UTC
Created attachment 16564 [details]
Xamarin iOS DocSync updates daily

Each day, when i open a Xamarin.Forms solution, the Xamarin iOS DocSync, begins to download, even that it finished yesterday, but it will repeat its download the next day, and if possible, add an option in the VS tools option, to manually disable it.

Recuse i have a "Performane & tuneup tool" that cleans the Temp folder daily as a cleanup:

So the DocSync folder:
will also get deleted.

or after the docs get downloaded, move them to another folder, and check that second folder before the download window begins.

also, now after the MS merger, maybe making the the Xamarin updates come with VS Notification area, might be a good idea.

Last, is there a link in "https://bugzilla.xamarin.com" that shows all the submitted issues by me?

Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2016-07-06 17:06:51 UTC
As a quick cross-reference (for slightly older Xamarin versions), one possible cause of recurring DocSync updates on XamarinVS 4.0, earlier Alpha and Beta versions of XamarinVS 4.1, and the current Alpha version of XamarinVS 4.2 is if the user name contains spaces: Bug 40754.

That particular bug is resolved in the Stable versions of XamarinVS 4.1 (although _not_ in the current Alpha version of XamarinVS 4.2).  Assuming that the reporting user in Comment 0 is on a recent Stable or Beta version, the cause of the recurring download behavior described in Comment 0 is likely a separate issue.  But I will add this cross-reference just to be thorough.  If the original reporting user gets a chance to add their precise Xamarin version number (for example from "Help > About Microsoft Visual Studio") in a follow-up comment, that wouldn't be a bad bit of extra thoroughness to complete.

## A tiny bit of additional info in case it might be useful

One little trick I've occasionally used in local experiments with DocSync is to intentionally block the download by making the download server "unresolvable."  In particular, I add a line to point to a local-network IP address: devimages.apple.com.edgekey.net

In the file:


## Link to submitted bugs

> is there a link in "https://bugzilla.xamarin.com" that shows all the submitted issues by me?

(This is a slightly modified version of the query linked under "Open bugs reported by me" on the Xamarin Bugzilla homepage: https://bugzilla.xamarin.com/.  This modified version includes _all_ resolution statuses rather than just open bugs.)

- Brendan
Xamarin Support
Comment 2 Jose Gallardo 2016-12-23 02:52:41 UTC
This was a confusing scenario basically driven by the notification from DocSync.
We've fixed it as part of Cycle 9 builds (XVS 4.3.x)
It's currently on the alpha channel.
If you're still facing this issue after updating to that (XVS 4.3.x) version, please feel free to reopen this issue.