Bug Project won't build using Xode15 release candidate.

Updating the Unity version in Unity hub from 2022.3.9f1 to 2022.3.10f1 will solve the problem immediately, with no extra hurdles.

 

Thank you so much - this did the trick for me! ... I updated MacOS and updated Unity to 2022.3.10f1 - now I'm happy building again!

 

Thanks a lot, this helped me.
Uninstalled xcode 15 and installed xcode 14.3.1
And I could build again

 

Hey there, I'm using XCode 15 RC, MacOS Ventura 13.6 and my iPhone 13 is iOS 17, using Unity 2021.2.5f
While the Xcode build is working, I cannot use Metal Frame Capture (I go to the Edit Scheme -> Options -> Capture GPU Frame -> select Metal, and in Build Configuration I select Release). Any idea why that is? This did work back in iOS 16 and XCode 14.3, while still using this same Unity version.

 

That works for me as well. Thanks, @dmarqs and @drewjosh for adding more details.
I'm using Unity 2023.1.16 + Xcode 15.0
And here is my contribution to make it even easier:

 

For everyone that is still experiencing the problem even if you've got Sonoma + Xcode 15.0 + 2022.3.10f1, try the following:

1. Quit Unity
2. From your game's iOS build folder, delete everything.
3. From your game's Unity main project folder, delete the Library and Temp folders.
4. Re-open your project and let Unity do all the re-importing.
5. Build again and see if it works.

 

I have the same problem here with Unity 2022.3.10 and Xcode 15 -> Two Errors :

- Assertion failed: (false && "compact unwind compressed function offset doesn't fit in 24 bits"), function operator(), file Layout.cpp, line 5758.

and

- Linker command failed with exit code 1 (use -v to see invocation)

 

Try adding the `-ld64` following the steps:
- https://forum.unity.com/threads/pro...release-candidate.1491761/page-2#post-9389312

 

Just like some here, this issue was not solved by upgrading Unity to 2022.3.10f1. In order to simplify the process for everyone here is a post build script to resolve the issue. Happy Coding!

Code (CSharp):

1. using System.IO;
2. using UnityEditor;
3. using UnityEditor.Callbacks;
4. using UnityEditor.iOS.Xcode;
5. using UnityEngine;
6.  
7. public class AppleBuildPostProcessor: MonoBehaviour {
8.   [PostProcessBuild(1)]
9.   public static void OnPostProcessBuild(BuildTarget target, string path) {
10.     if (target == BuildTarget.iOS) {
11.       ModifyValues(path);
12.     }
13.   }
14.  
15.   private static void ModifyValues(string path) {
16.     var projectPath = PBXProject.GetPBXProjectPath(path);
17.     var project = new PBXProject();
18.     project.ReadFromFile(projectPath);
19.  
20.     project.AddBuildProperty(frameworkTargetGuid, "OTHER_LDFLAGS", "-ld64");
21.  
22.     project.WriteToFile(projectPath);
23.   }
24. }

 

This breaks Odin Serialisation on iOS.

 

this seems no longer true

 

Sonoma, xcode15,
Report https://issuetracker.unity3d.com/is...latforms-fails-with-xcode-15-dot-0b6-or-newer implies that the issue has been fixed.

I am still getting:

ld: Assertion failed: (false && "compact unwind compressed function offset doesn't fit in 24 bits"), function operator(), file Layout.cpp, line 5758.



clang: error: linker command failed with exit code 1 (use -v to see invocation)

The solution is not to write hacky post process scripts or

-ld_classic

flags, butUnity should fix the issue to their product.

 

Download Xcode beta 15 version 5 and placing it in the Applications folder worked for me.
Plus
> Unity Framework > Build Settings > Other Linker Flags (you can search for it) > double click on value + hit plus on button > add "-ld64" > hit Enter >

 

This isn't solving it for me with Xcode 15.0.1 and Unity 2022.3.11f1. Having Beta 5 alongside the latest version was working until these latest updates, and now it's broken again with the same errors.

Assertion failed: (false && "compact unwind compressed function offset doesn't fit in 24 bits"), function operator(), file Layout.cpp, line 5758.

Linker command failed with exit code 1 (use -v to see invocation)

 

Did you add "-ld64" or "-ld_classic" in other linker flags for Unity Framework?
Also, please share the detailed screen shot of the error. Thanks

 

These flags break functionality in Odin Serialization and who knows what else. My fix right now is to go back to xcode 14 which doesnt work on sonoma.

 

It appears from my own testing that the -ld64 or -ld_classic linker is only needed if the minimum iOS target is less than 15.0. Whether or not you want to exclude anyone on iOS 14 and below is another question.

 

Upgrading from 2023.1.12f1 to 2023.1.18f1 fixed it for me.

 

Unfortunately not for us, but with the workaround (-ld64) it works.

 

The issue was resolved with 2022.3.10f1 for us and reappeared with 2022.3.11f1. The workaround seems to work in our case.

 

Upgrading from 2022.3.6f1 to 2022.3.13f1 fixed it for me.

XCode 15.0.1 apple silicon

 

Upgrading from 2022.3.6f1 to 2022.3.13f1 did not work for me. and i'm also on XCode 15.0.1 apple silicon.

Are there any other solutions?

 

Unfortunatly it seems not. 2022.3.13f1 and Xcode 15.0.1 still give the assertion error.
The -ld_classic trick is working only when you build brand new Xcode project. If you get error once and do the trick after it won't work.

 

Here's an update to my situation. I was finally able to get a build from unity to archive and push to TestFlight. The solution (or what i think fixed it) was to remove the compiler flags that Unity's standard assets use for mobile devices (CROSS_PLATFORM_INPUT, and MOBILE_INPUT). Now i'll still have to replace the code so my app will function, but after I did that I was able to use 2022.3.13f1 and Xcode 15.0.1 to make an iOS build and push to TestFlight. Is there anybody that confirm what I've seen?

 

A workaround worked for me is by commenting the first three lines in the SignInWithApplePostprocessor class and add the AuthenticationServices.framework to the link binary to UnityFramework and add Sign in with Apple capability to the Unity-iPhone in Signing & Capabilities:

// #if UNITY_IOS || UNITY_TVOS
// #define UNITY_XCODE_EXTENSIONS_AVAILABLE
// #endif

 

This also happens to me with

• Unity 2022.3.13f1
• Xcode 15.0.1

But only when setting Managed Stripping Level to "Medium" or "High".
It Does not happen on levels "Minimal" or "Low".

 

For me what seemed to work was updating Unity from v2022.3.11f1 to v2022.3.14f1
Then reinstalling Xcode to v15.0.1

Then in Xcode under PROJECT select Unity-iPhone, select the Build Settings and search for "Other Linker Flags" and double click it, then add "-ld64" to it. (-LD64, not -ID64)

The project archived successfully, but it gave me an error when uploading it to AppStore Connect.
I fixed this issue by selecting "UnityFramework", then in Build Settings set "Always Embed Swift Standard Libraries" to No

 

nice one but how do you find "frameworkTargetGuid" is there a missing part of the code ?

 

ok found it just add.

Code (CSharp):

1. var frameworkTargetGuid = project.GetUnityFrameworkTargetGuid()

before the AddBuildProperty

 

The error re-appeared for me with Unity 2022.3.13f1 when trying to build an existing iOS app for visionOS. The -ld_classic trick did not work.

 

This is still an issue with my projects as of Unity 2022.3.14f1 and Xcode 15.0.1. The suggested linker flags don't work.

 

It's gotten to the point that for every unity build I make for iOS, I have to delete the xcode project, build, add the missing linker, and only then can I build and archive. But if a single build failure occurs I have to start the whole process again. I don't understand how something this simple is still an issue with unity. And yes, I think its on unity to fix this since it's the one building the initial project. Having to hack a post process for this is ridiculous. Can some one at unity at least confirm if they care about fixing this? I've been having this issue for the past 4 or 5 unity versions.

 

Thank you , for complete understanding , it helped out

 

after updating mac os I get the same problem,I not understand why every time apple try so hard to make problems on EVERYTHING

put -ld64 NOT WORK form me
there is any other solution for this?
I am on unity 2023.1.13

 

I try adding this code:

1. var frameworkTargetGuid = project.GetUnityFrameworkTargetGuid()

But STILL have the error: "PhaseScriptExecution failed with a nonzero exit code"

 

did you solve with the -ld64 flag? because that not work for me

 

Same issue. A brand new Unity project and I can not Build and Run.

Changing to Target SDK: Simulator SDK and/or -ld64 does not work.

Mac M1
XCode - Version 15.0.1 (15A507)
Unity - 2022.3.15f1

XCode Produces errors like:

Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase.

Sandbox: il2cpp(51172) deny(1) file-read-data /Users/Mada/_games/x/Il2CppOutputProject/IL2CPP/build/deploy_arm64/il2cpp

 

I updated the iOS of my test device to v17.2 and was forced to update to XCode 15 and had the exact same problem. No matter what I tried suggested here or in other threads, helped me to solve the error.

In my case I got the:
DT_TOOLCHAIN_DIR cannot be used to evaluate LIBRARY_SEARCH_PATHS, use TOOLCHAIN_DIR

It appeared for pretty much every SDK I was using like Applovin, Firebase, Facebook... even if I manually changed those to TOOLCHAIN_DIR, it wouldn't build.

Today I finally solved it and results that the problem actually is with Cocoapods (who would have thought ). So forget about post processor build scripts or any other solution you find here. What you need to do is to install the correct Cocoapods version corresponding to your Unity editor.

You might want to update first to the latest Unity LTS version of your choice.

Then to solve the error do this:

1. Open Terminal and type:

Code (CSharp):

1. gem list

2. Delete all listed packages related to Cocoapods:


By typing:

Code (CSharp):

1. gem uninstall cocoapods
2. gem uninstall cocoapods-core
3. gem uninstall cocoapods-deintegrate
4. gem uninstall cocoapods-downloader
5. gem uninstall cocoapods-plugins
6. gem uninstall cocoapods-search
7. gem uninstall cocoapods-trunk
8. gem uninstall cocoapods-try

In case you do not have permission use "sudo gem uninstall cocoapods" instead.

3. After deleting all cocoapods packages go back to unity. Then Assets -> External dependency manager -> IOS resolver -> Install Cocoapods

4. (optional) Make sure that cocoapods installed correctly by typing 'pod' in your terminal, if it says that command was not found then run 'sudo gem install cocoapods'

I use Unity 2022 LTS and it installed Cocoapods v1.14.3.
I exported my game into an entirely fresh folder and everything runs smooth again. I do not use -ld64 or anything else.

Original source from another cocoapods problem:
https://forum.unity.com/threads/ios...ods-installation-failure.483511/#post-6548239

 

Had this issue and I can confirm that the cocoapods solution works.

Here's a link to install google's external dependency manager unitypackage:

https://github.com/googlesamples/unity-jar-resolver

It will correctly update cocoapods for iOS builds on M1 macs (my case) hopefully this helps.

 

I faced this issue for 2 - 3 hours these steps fixed for me;

• Upgrade Unity Editor version 2022.3.8f1 to 2022.3.17f1
• Add
  Code (CSharp):

  1. -ls
  command line to Xcode UnityFramework/BuildSettings/Linking-General/OtherLinkerFlags/Debug/ "Last Line"

 

This worked for my project.

 

@waldgeist

Did you try updating to Unity 2022.3.18? And did you try the workaround mentioned earlier?

My system:
- Apple M1 Max
- macoS 14.3
- Unity 2022.3.18
- Xcode 15.2

I currently don't have to do the workaround anymore to build successfully, which is great

 

Tell me please. Is this still a mistake? And how can I fix it? I can’t even build an empty project on Xcode 15, Sonoma M2. Thank you!

 

2023.1.16f1 , 2022.3.19f1 , 2022.3.18f1

 

I didn’t understand what specific target should be set to (no), I set it to everything, the build started moving and started processing, but then the error occurred again. Thanks!