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.
Inside IDE, typing UIWindow.Notifications does not show up in intellisense.
Other new APIs, like:
o.Retai... does not work either.
Navigating to the Assembly Browser does show these APIs are available, and the code compiles fine.
Which md version ?
Is the reference correctly set -or are you using transitive references (which compile fine atm, but are incorrect) ?
Perhaps the new code completion system did not detect that the framework assemblies had been updated?
y, we had a bug with .dll updates - but that should've been fixed in 3.0.3.x
Therefore the information about the version is important.
I am running MD 18.104.22.168.
Is there anything you want me to run / test to confirm it might be a code completion issue?
Is there a workaround for now to reset the cached assembly completion info that Stuart can use?
Couldn't find any obvious files in Caches, etc - would be much appreciated!
As a workaround you can delete the code completion caches: ~/Library/Caches/MonoDevelop-3.0/DerivedData
It was 3:30 AM, so perhaps that is why I missed it in ~/Library/Caches the first time :)
Did it help to remove the cache ?
I checked the history - good news - the bug is already fixed.
Bad news - we didn't ship the fixed version :(
*** This bug has been marked as a duplicate of bug 5558 ***
Yes indeed - removing cache resolved the issue.