Search Issue Tracker
Duplicate
Votes
0
Found in
2018.3.0a1
2018.3.8f1
2019.1
2019.2
2019.3
Issue ID
1140502
Regression
No
"System.IO.FileSystemWatcher" not implemented on .NET 4.x API
Reproduction steps:
1. Open "fstest.zip" project
2. Build & Run Standalone build
3. Observe the "NotImplementedException: The method or operation is not implemented." error
Expected Result: "System.IO.FileSystemWatcher" is implemented
Reproduced with: 2019.3.0a1, 2019.2.0a14, 2019.1.1f1, 2018.3.14f1
Did not reproduce on: 2017.4.26f1 (IL2CPP only implemented from 2018.3)
Comments (1)
-
Classplash
Oct 21, 2019 10:29
This seems fixed in the 2019.3 beta. Will it be backported to 2018 LTS and 2019.2? We can't update to a beta and these are our only options.
Additionally, this issue is marked as a duplicate but it contains additional info / seems different.
1. It mentions Standalone builds. The other issue doesn't mention the platform.
2. the other issue says ".NET 4.x with .NET Standard 2.0 only" and I'm not sure what that means. We were never using .NET Standard 2.0 and still had this problem.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "New" Label overlaps long Asset names in Import Unity Package Window
- Rotation values flip in animation when importing FBX with a generic rig
- [Quality Hackweek] Activated Terrain Inspector is active only until the terrain GameObject is deselected when two or more Inspectors are open
- Physics Used Memory keeps growing when GameObject colliders are enabled and disabled
- Errors are thrown and Inspector's UI element is not drawing when a GameObject with script component using a List<T> attached is selected
This is a duplicate of issue #1066732