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.
Steps to reproduce:
1. MonoTouch should be installed
1. Delete com.apple.adc.documentation.AppleiOS5_0.iOSLibrary.docset from path com.apple.adc.documentation.AppleiOS5_0.iOSLibrary.docset.
2. Delete apple-doc-wizard.sh from Developer/MonoTouch/usr/share/doc/MonoTouch
3. Go to Help->click on help.
After deleting these files go to help->click on help then user is not prompted to documentation wizard pop up.
User should prompt to documentation wizard pop up.
XS 4.0.6 (build 3)- fd96c44d878d1e176954e062c9ee658c6fe7d47b
Mono 3.0.11 ((no/edc181c)
Not sure why you're doing step 2. Can you confirm that this happens without performing step 2?
An update to the above issue , We have also checked it without deleting step 2
We are seeing same behaviour here.
I also see this behavior. Perhaps the merge-reset steps have changed. I'll have to check with Jeremie when he gets in today.
Also, the MonoDoc stuff is Xamarin Studio, not iOS (for future reference).
So yeah, deleting the Apple documentation was not a sufficient condition for triggering the merge, so this bug is invalid.
The condition that should be triggering the merge here is that there is no merge.status.
RESOLVEing this one as INVALID.
Jeremie is committing the fixes right now, so you can re-test with the next 4.0.6 build.
As per comment 4 marked this as Verified Invalid.