I'm getting an error on the IL2CPP Mac build (see below). It looks like the it's not finding the file because of the space in the filename. Running Unity 2019.4.5, MacOS 10.15.5 Temp/StagingArea/Thousand Threads.app/Contents/Frameworks/GameAssembly.dylib: failed to link debug symbols stdout: stderr: error: cannot parse the debug map for 'Temp/StagingArea/Thousand': No such file or directory UnityEditor.OSXStandalone.OSXDesktopStandalonePostProcessor:ProcessPlatformSpecificIL2CPPOutput(BuildPostProcessArgs) DesktopStandalonePostProcessor:ProcessIl2CppOutputForBinary(BuildPostProcessArgs) (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/DesktopStandalonePostProcessor.cs:287) DesktopStandalonePostProcessor:SetupStagingArea(BuildPostProcessArgs, HashSet`1) (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/DesktopStandalonePostProcessor.cs:231) DesktopStandalonePostProcessor:PostProcess(BuildPostProcessArgs) (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/DesktopStandalonePostProcessor.cs:42) UnityEditor.BuildPipeline:BuildPlayer(BuildPlayerOptions) Builder:Build(String, BuildTargetGroup, BuildTarget, ScriptingImplementation, String, Action, Action) (at Assets/Editor/Builder.cs:73) Builder:BuildMacAppStore() (at Assets/Editor/Builder.cs:199)
Oh man, can we have a bug report on this? In the mean time, should be able to work around it by removing the space from the project name.