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
GitHub or 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.
We're using Mono for cross-platform development and have a critical requirement for a FileSystemWatcher.
I'm alarmed at the current state of FileSystemWatcher. There's little documentation of the issues on a Mac, but it's clear there's a number of issues with the OSX FileSystemWatcher:
- Only CreateFile events are detected. This is completely inadequate
- Sub-folders aren't reliably tracker. Again this is can't be considered a FileSystemWatcher implementation and certainly nowhere near the .Net equivalent.
- It uses kQueue as the backend. This is considered inapproriate. It should use the new fsEvents on Macs.
Moreover, there are a few implemnetations of fsevents FileWatchers on the Mac. We've researched them, but I'm nervous about using them. Could they at least be used as a start for the implementation on Mac (I'm thinking SparkleShare).
This is a big issue for us and greatly hinders out use of Mono on Mac.
Note we've tested again 3.0.1 -> 3.0.3. All are affected.
We are still waiting for an official implementation. For now we're working with Zip archives from Xaramin against the licensed dll....
This has been fixed with the release of the official FSEvents component with Xam.MAc 1.2
The issue still exists for subfolders that exist at the time the FSWatcher is created..
Every subfolder of the root folder is ignored, only those which are created when the FSWatcher is working are properly watched