Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 or GitHub 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.
( this is a copy & paste from XS forum ; at least one more user reported the same problem )
I am on the latest alpha w/ iOS7 sw stack .
Here's what happens :
In XS, I click on Help/API Documentation
MonoDoc starts up and prompts me : 'Documentation Update available' with choices Remind me later/ Update now
I choose Update now; continues with 'Merging Apple Docummentation' then 'Update Successful. Restart MonoDoc for changes to take effect' with choice Restart MacDoc
I choose Restart MacDoc; and I go back to step 2, above.
I've noticed this MonoDoc behaviour since the very first installation, few weeks ago, but I kept ignored it in order to let the official iOS7 / Xcode / Xamarin sw be released and then see if the problem fixed itself.
*** Bug 14952 has been marked as a duplicate of this bug. ***
*** Bug 14958 has been marked as a duplicate of this bug. ***
I have just downloaded and installed Xamarin.iOS 7.0.3 , where it states that Fix iOS7 documentation downloading/merging but, unfortunately, for me it still goes into a kind of infinite loop , as per my original explanation, above.
Is there a MonoDoc log file I can track and maybe send it to you for diagnosis ?
I have re-assigned the bug to the person who can answer you related to that latest change.
What version of Xamarin Studio are you running on together with the X.iOS update? If you can indeed attach your MacDoc log file, it is located in ~/Library/Logs/MacDoc.
Created attachment 5178 [details]
October MacDoc logs
This attachment contains all the MacDoc files generated this month ( about 6 ) , out of which four were generate today over the latest alpha XS and X.iOS.
Thanks for your prompt reply and action.
Below are the details as per the XS About box.
Also, I just attached the file generated in October by MacDoc. The older ones are for history purposes ( to put the issue in a history context ) .
Today's ones ( October 19 ) are attempts to run the MacDoc refresh over the latest XS alpha and X.iOS, as per the below details :
Version 4.1.12 (build 6)
Installation UUID: 6dada051-646e-4b0d-a13d-48a86bbcaf96
Mono 3.2.3 ((no/8d3b4b7)
GTK+ 2.24.20 theme: Raleigh
Package version: 302030000
Apple Developer Tools
Xcode 5.0 (3332.25)
Xamarin.Mac: Not Installed
Version: 4.10.0 (Starter Edition)
Android SDK: /Users/********/Library/Developer/Xamarin/android-sdk-mac_x86
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
4.0.3 (API level 15)
Java SDK: /usr
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
Version: 220.127.116.11 (Indie Edition)
Build date: 2013-18-10 17:54:48-0400
Release ID: 401120006
Git revision: a9ae69a4bf37955e4ab4df0cec7804f574c51f72
Build date: 2013-09-25 16:59:37+0000
Xamarin addins: 761ae26f220068dda0b62f0dd2253f617589a8c6
Mac OS X 10.8.5
Darwin ivrb01.local 12.5.0 Darwin Kernel Version 12.5.0
Sun Sep 29 13:33:47 PDT 2013
Thank you. Ionut.
The new system requires a Xamarin Studio that comes with the new MonoDoc.
Jeremie, did this make it into the 4.1.12 build?
Today, we have checked this issue with following builds:
XS 4.0.14 (build 5)
Mono 3.2.4 ((no/f163333)
Now, this is working fine Observe that mac doc is updating successfully and it not prompts again for Documentation Update Available.
Hence marking this as verified