Bug 16854 - Log files grow infinitely, eventually causing debugging iOS apps from VS to fail
Summary: Log files grow infinitely, eventually causing debugging iOS apps from VS to fail
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.8.x
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: vsx
Depends on:
Reported: 2013-12-17 13:39 UTC by David Hathaway
Modified: 2016-02-23 20:26 UTC (History)
7 users (show)

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:

Description David Hathaway 2013-12-17 13:39:27 UTC
I think this is a duplicate, but I couldn't find the original bug.  When developing iOS apps in Visual Studio, the log files grow infinitely, continually appending to the same log files.  These files are constantly being copied back and forth between the servers.  Eventually, this gets to a point where VS is no longer able to connect to the Mac build host.

The files in question are in the following folder on the Mac:


After removing these file, VS then displays the option to "Clean remote build logs".  Apparently, once the log files grow to much, even that feature no longer works.

The following thread in forums also notes this:

Comment 1 Jose Gallardo 2016-02-23 20:26:24 UTC
The log generation has changed since this bug has been reported and it works quite differently now, without endless growing up files.

Marking the bug as resolved.