After upgrading to 2022.2.0 I tried to make a ios build.
When Archiving I immediatelly got the error:
bee_backend: no such file or directory
Same error here. I think itās due to the change with the compiling and il2cpp, but no idea how to resolve it
Hereās my bug report tracker for this issue, please go vote on it!
Same here when compiling iOS on my PC and moving it to my Mac, opening in XCode and building. I installed Unity on my Mac, loaded my project and built the iOS target, opened it in XCode and it is doing really odd things. Tends to hang forever on an early step in the Build Process. Occasionally it will finish, but then it isnāt respecting settings in Xcode such as Portrait vs Landscape. Had none of these issues in earlier versions.
Tried on Windows 10 and 11 with 2022.2.0. Mac is OS 12.6 with Xcode 13.4. Thanks!
On a whim I reinstalled the Mac OS and XCode 14 from the App store (as Iād read doing it manually can lead to it being in the /Developer folder and not the /Application folder, and Unity may have accidentally hardcoded some paths. This did not change any behavior. I did try moving my Unity iOS build output folder off the desktop and its no longer hanging in the execution of Build scripts, but it is still giving me bee_backend errors.
Downgrading right now would be time consuming and painful, so Iām hoping someone has some insight here. Thanks!
Hereās a clue Iām copying from another post of mine, but I havenāt figured out any way around it yet. Maybe someone from Unity can chime in:
Iām assuming this has to do with this part of the 2022.2 update:
iOS: Changed IOS Xcode projects to use the il2cpp executable to compile il2cpp sources, so the Xcode doesn't compile the sources directly. This makes iOS consistent with other platforms.
Iām using Windows 11 Unity to build my iOS project, which I then import onto a Mac OS device (via VMWare virtual machine). I open a new terminal in the project folder and run a pod install command to get the workspace file, then archive. This process has always worked in 2022.1 but now it doesnāt.
I noticed the xCode project is setup differently, with a new target called āGameAssemblyā and thereās a script attempting to run on it in a file directory that doesnāt exist:
Itās looking for the C: drive which doenāt exist on this machine. I tried copying over the data file and replacing the file path with the filepath of the data folder on the Mac OS, but that didnāt work either.
I tried copying over the directories itās looking for, even transplanted it into a previous project, but that didnāt work either
I downgraded my project back to 2022.1.23f1 and confirmed it still builds and runs fine on iOS. And I confirmed a blank Core 2D URP project works as well. So this is certainly specific to 2022.2 and the 2023 beta builds.
But I duplicated this in Unity running on the Mac directly with a new blank 2022.2 Core 2D URP project, so it seems unlikely to be related to Windows pathing issues or leftover garbage in the build process.
Are we the only people trying out iOS with 2022.2+ ? I canāt believe something this much of a show-stopper was missed in the releaseā¦ Ahh well, Iām working on a bug report in hopes it catches someoneās attention.
Digging deeper though, my flavor of this issue does appear to be related to messed up pathing/folder naming. The initial error was due to the folder IL2CppOutputProject.ā¦\bee_backend\mac-x86_64 being incorrectly named mac-64. So I manually changed the folder name, and now I get a Parent called on an empty path at NiceIO.NPath.get_Parent() in /Users/bokken/build/output/unity/il2cpp/Unity.IL2CPP.Common35/NiceIO.cs
No clue how to debug that one. None of these errors are resolving to useful stuff on Google or in the Reported Issues database. Hopefully someone comes along with more insight here, but for now Iām just going to hang out on the earlier version.
Bug Report Sentā¦ though they must have a slow pipeā¦the 7Zip of my project (300MB) is unlikely to get there anytime soon.
Same problem here. Looking at release notes for 2022.2 I see that builds are to be made with XCode13 (now replaced with XCode14), however XCode13 doesnāt natively support iOS16+ builds so everythingās kinda uncertain. Hope this is fixed soon, really annoying not to be able to make use of all new features in 2022.2 for iOS builds.
1 Like
Yeah, youād think this would be a rather large, showstopper bug. Iāve not seen any response to the Bug report I submitted from within Unity yet.
1 Like
I got the same error with 2022.2.1. At first the error says that folder āmac-x86_64ā not existing, and I manully renamed it from āmac-x64ā, and then the 2nd error comes:
System.InvalidOperationException: Parent called on an empty path
at NiceIO.NPath.get_Parent() in /Users/bokken/build/output/unity/il2cpp/Unity.IL2CPP.Common35/NiceIO.cs
getting similar issue here too for mac builds
Not to be mean or anything, but my project has been building just fine with 2022.2 and 2023.1. I was using an Apple Silicon Mac with macOS 13.
Could you tell us more about the project, my issues were ocurring on 2022.2+ using SRP & ARKit/ArFoundation. Perhaps the build issue happens when compiling from a Windows editor, beats me 
If youāll read my explanation above, I tried compiling blank projects created in Unity on the Mac directly, as well as pre-compiled in Windows with similar results. Iāve spoken to a handful of people successfully compiling in 2022.2+ but none have yet provided any details that would help identify what is different. In one case I did a fresh install of OSX, XCode, Unity and it still failed with the same mis-named directories.
What version of MacOS are you running? What version of XCode? Are you doing anything other than opening the XCode project, changing the signing configuration and compiling?
M1 Max 16-in MacBook Pro, macOS 13.1, Xcode 14.2. My project was brought up all the way from 2021 release, one major version at a time, over time. My project does not use AR features (I specifically disabled any unused packages from the project), but it does have some plugins that do post-build modifications on the Xcode project file. As my signing identity was configured in the Unity player settings, it was set correctly in the Xcode project, and I can simply compile to run.
As for replicating the issue, I was investigating other Unity issues and made several projects and built them on iOS just fine, so I cannot replicate the issue you are seeing.
To @Juanson: As for why I mentioned me using Apple Silicon, because I saw you were trying to match a x86_64 path, so I assumed you were building on an Intel Mac. As my Mac is Apple Silicon, it could have been where the difference is, and I thought it would have been obvious for you to notice.
That appears to be the issue. Unity compiles no longer function on Intel based Macs. M1/2 core compilation works fine. Can anyone else please confirm?
Just chiming here that we are seeing the same problem. Unable to compile with the following error reported:
chmod: dropXcode/Builds/Il2CppOutputProject/IL2CPP/build/deploy_x86_64/bee_backend/mac-x86_64/bee_backend: No such file or directory
To confirm, are you building this on an M1/2 mac?
Just to chime in ^2, Iām getting this issue on m1 mac when building for mac.
I made a post that is probably related to this issue (it hasnāt got any attention, but Iām urgently waiting for it to be fixed)
Thanks for the details. Could you submit a bug report for both issues? I donāt think we have a bug report for either of them. Maybe two separate bug reports would be good, as they might be different issues.
Not M1/2 this is in Intel VM hardware and building for iOS.
Upgraded from 2021.3.11f1
More information so we are building on Windows Unity to create the XCode project and then running on Mac Intel VM to build for iOS.
I notice that the UnityHub on Mac now has the option to install silicon Unity and I wonder if this is the difference. I am about to try building on Unity Silicon and see if that changes things.
1 Like
I can confirm that the same project built on M1 machine builds with out a problem.
If I can find the time to put together a sample project, build on Intel and transfer XCode to M1 machine and build see what happens I will.
But I confirm that project built on 2015 macbook pro failed with:
dropXcode/Builds/Il2CppOutputProject/IL2CPP/build/deploy_x86_64/bee_backend/mac-x86_64/bee_backend: No such file or directory
Built on M1 Mac Mini
Works
Monterey
Unity 2022.2.1f iOS
XCode 14.1