Unity Command Line Build Fails on Catalina

Unity Engine
,
1

On Catalina our command line build now fails with the following error.

/Applications/Unity/Hub/Editor/2019.2.2f1/Unity.app/Contents/MacOS/Unity -batchmode -nographics -quit -projectPath SimpleScene/ -executeMethod AutoBuild.Build

Refresh: detecting if any assets need to be imported or removed ...

Refresh Completed time: 0.038818s
    Asset Scan time: 0.038416s
    Asset Hashing: 0.000000s [0 B, 0.000000 mb/s]
    Asset Import (Scripting) time: 0.000000s (count: 0)
    Post Processs Assets (Scripting) time: 0.000000s
    Asset Rehashing: 0.000000s [0 B, 0.000000 mb/s]
    Asset Import (Non Scripting) time: 0.000000s (count: 0)
    Post Process Assets (Non Scripting) time: 0.000000s
    Dependent Assets to Import Queue time: 0.000000s

[Package Manager] Server::Kill -- Server was shutdown
Cleanup mono
debugger-agent: Unable to listen on 28
[usbmuxd] Stop listen thread
[usbmuxd] Error:
[usbmuxd] Listen thread exiting
Checking for leaked weakptr:
  Found no leaked weakptrs.

Notice the error…debugger-agent: Unable to listen on 28

I suspect this just masking another error.

Since upgrading, our automated build is down. Does anyone have any ideas on a solution? It seems even the simplest project fails.

2

Hey, after upgrading to Catalina, I can’t build a player manually.

The Unity console throws following errors when build :

And this error occurs when the disk space is not enough.
It seems like Catalina’s new security protocol that restricts access to disk spaces is causing this issue.

3

@NGC6543 Is this even with a new blank project ?

@RedRory Is this only on the commandline ? or does this also break when using the build window in the editor ? am wanting to narrow down where the possible issue is. I have verified that I can build the player on 2017.4/2018.4/2019.3 on MacOS 10.15 within the editor.

4

Hi @andrews_unity
I tried to build iOS on a new empty project (2019.2.8f1), and it failed with following errors :
Settings : .NET 4.x, Linear Colorspace, Metal API. No other settings were changed and no other packages were imported.

As you can see, the error message says that the disk is full.
But my system has free space of over 800GigaBytes!
5054159--495995--스크린샷 2019-10-11 오전 10.41.13.png
Also, I set Both Unity Hub and Unity.app grant access to entire disk space.

5

Thanks @NGC6543 I will look into this could be specific to iOS, can you check and see if you can build a standalone mac build ?

6

Sorry I didn’t get in touch with you soon. It seems like the new macOS Catalina has some critical bugs with FusionDrive. After inquiring Apple support they suggested that I should downgrade the OS to Mojave.

Thanks again for your help. I’ll try the upgrade some other time.

7

Sorry for the late reply. We build fine from the Build Window. It is just command line that is causing problems.

8

We are having a similar problem with running commands from Unity on Catalina. Was there an answer for this that was never posted @andrews_unity ?

9

@BuzzJive can you provide some more details, have you verified this doesn’t work with the latest 2019.3 betas ?

10

In case anyone experiencing similar disk space error on macOS Catalina, here’s the solution :

  • Create a bootable USB for macOS Catalina 10.15.1 or higher
  • Reboot system with USB
  • Open Terminal and reset FusionDrive (Follow this guide)
  • Re-install Catalina

! This procedure clears the disk space, so be sure to backup your data if needed!