Current macOS 10.13 High Sierra support summary:

macOS 10.13 High Sierra upgrade recommendation: upgrade with care
For macOS 10.13 support you have to upgrade your Unity Editor to one of these versions:

Patches for Unity Editor can be downloaded at usual place: Download Archive

There will be no Unity 5.4.x fixes for High Sierra, you have to either keep your machines on macOS 10.12 or upgrade your project to Unity 5.5.x and later. In general 5.4.x and older Unity versions might work with High Sierra on HFS+ disk, but it should be considered as last resort workaround if you have to use older Unity versions on new OS.

Xcode 9 works fine with macOS 10.12.6, so if you are in late development stages of your game, it’s still recommended to stay on macOS 10.12.

Other known problems, but not related to OS upgrade:
- Global cross platform Unity Editor outage while opening project. Workaround: disable networking while opening project. There will be blogpost on this issue. Should be fixed by now on our backend servers.

Original post:

We are aware of some issues with Unity and macOS 10.13 (High Sierra) beta 1 release. We recommend waiting before updating to this macOS version until we finish investigating reported issues, one of which being trouble with assets appearing in Project View. Check back here soon – we’ll keep updating this post as we learn more.
Update: we were able to track down missing Project View items issue as APFS and Unity editor interoperability problem. We are working on a fix, though meanwhile we recommend to not upgrade your main filesystem to APFS or at least keep Unity editor and your projects on HFS+ partition.
Update2: we have updated our Mac VR build with APFS fix. You can get it there:
http://beta.unity3d.com/download/f196ae3d2614/public_download.html . Fixes for other Unity versions will follow shortly.

P.S. you don’t need to upgrade to macOS 10.13 to try new Xcode or iOS 11. Just keep using 10.12.
P.P.S. general advice while testing beta OS’es, please consider installing it to separate partition to not interrupt your everyday workflow.

I updated post with new details:

Wow, does this mean all old builds of Unity will stop working that are older than the current one once 10.13 is out (if people do the recommended thing and use APFS)?

Man… good thing I won’t need 5.3.4p1 soon.

For older versions, presumably you could make a small partition formatted with HFS+ and run them from that.

Now is probably a good time to remove x86 and Universal options for Mac builds, and just leave x86_64.

–Eric

as Mantas-Puida confirmed also, please note that I have found that moving only the Unity project to non-APFS partition is NOT sufficient (project can be loaded, assets show up, but cryptic build errors ensue) – had to also copy the Unity application directory to non-APFS partition and run from there, after which all was well.

MacVR preview build #2 adds APFS compatibility fix/workaround, we’ll need to talk with Apple if it’s a genuine kernel bug.

https://forum.unity3d.com/threads/vr-on-macos-preview-build.474381/

MacVR preview build #2 adds APFS compatibility fix/workaround, we’ll need to talk with Apple if it’s a genuine kernel bug.

https://forum.unity3d.com/threads/vr-on-macos-preview-build.474381/

Hi, I have noticed that this version still not support APFS. Well do you have any plan to support APFS and could I ask how long it might take?

Hi, I have noticed that this version still not support APFS. Well do you have any plan to support APFS and could I ask how long it might take?

It’s hard to extract any new information of the problem you’re seeing from this alone. If possible, file a bug, explain
the details of your filesystem (“diskutil info /” output when running on macOS High Sierra, path where you’re using the project from, project itself causing problems embedded), does creating a new empty project work, does importing the old project work when project Library folder is removed etc. Thanks!

Fixes for Unity editor are in flight. We are still investigating Monodevelop issues.

A work around here is use the latest MonoDevelop 6.1. Seems like the 6.1 (or Xamarin Studio) works really good.
You just need to change the scripting tool to Xamarin Studio in Unity → Preference to use it. It works pretty fun for me.

You can get it here : http://www.monodevelop.com/download/

A work around here is use the latest MonoDevelop 6.1. Seems like the 6.1 (or Xamarin Studio) works really good.
You just need to change the scripting tool to Xamarin Studio in Unity → Preference to use it. It works pretty fun for me.

You can get it here : http://www.monodevelop.com/download/

This works