Bug XCode build error after upgrading to 2022.2.0

Your answers are helpful, thanks

 

Worth noting :

• Starting with Xcode 14, bitcode is no longer required for watchOS and tvOS applications, and the App Store no longer accepts bitcode submissions from Xcode 14.

 

Just did a test with the recently released Unity 2022.2.9f1 version

And guess what:
This postbuild processor fix is STILL required when exporting an iOS build on windows

Unity is completely dropping the ball on this one !
I ' am a pro customer since 13 yrs and it really makes me not feeling too comfy if products i use and love for such a long period degrade quality wise !
On top of that it's a bit irritating that we already had Unity staff stepping in here, so they are aware
about it,but do not seem to care that much because they build on Mac OS ...

 

It's insane that this is still broken. <deep sigh>

 

Can you give more detailed info on what to do with this code and where to put it please?

 

On to another testround using recently released Unity 2022.2.10f1 version
Honestly, i do not have much hope, there's nothing in the readme at all about the problem

Has all the iOS team sacked ?

Update:
As excepted, same problem persists in Unity 2022.2.10f1 ...
disappointed...

 

Just ran into both of these issues and after submitting bug reports for _both_ of them found this thread. This is really annoying and its sad that no one seemed to test this before released 2022.2 into the wild. It seems to me as if building on an Intel mac should be a standard procedure as should be transferring the IL2CPP output to a Mac for building and therefore should be part of the standard suite of regressions tests. I hope it is now.

Especially annoying is that the datapath by default gets hardcoded to the directory on the machine running Unity _inside_ the Unity project. Not even relative to the build output itself. Something I completely don't understand.

 

I'm sorry if this is a bit ranty. But now that I've read the whole topic and especially the dates I'm extremely confounded not only how this could have passed QA to begin with, but how such a simple thing can take more than 4 months to fix.

I mean the workaround as posted in this thread on page two is _five_ lines of code. How hard can it be to actually fix it if the workaround is _five_ lines of postprocessing.

Code (CSharp):

1.                
2. string sPath = PBXProject.GetPBXProjectPath(path);
3. var projRaw = File.ReadAllText(sPath);
4. projRaw = projRaw.Replace("chmod +x \\\"$IL2CPP\\\"", "chmod -R +x *\\nchmod +x \\\"$IL2CPP\\\"");
5. projRaw = Regex.Replace(projRaw, "--data-folder=\\\\\"([^\"]*)\\\\\"", "--data-folder=\\\"$PROJECT_DIR/Data/Managed\\\"");
6. File.WriteAllText (sPath, projRaw);
7.  

I'm wondering how this isn't a show stopping major issue at the top of the stack if your build system is broken for a complete platform for anyone not running the build on a specific type of architecture (arm) or crossbuilding from a different PC.

 

Just for completeness - not that i expected anything else:

I did another testround using recently released Unity 2022.2.11f1 version
Same problem persists in Unity 2022.2.11f1 ...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

disappointed...

 

Another release - another try - another FAIL !

Testing Unity 2022.2.12f1, same problem still persists ...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

Another disappointment....

 

It is insane, can't believe that I'm seeing such a crap from Unity team not fixed for ages. How it is possible? Is there a support tickets somewhere?

Having same issue, will downgrade project to 2021 coz this + another issues in iOS build process

 

2022.1.24 works fine.

 

@AlienMe That's because this issue was introduced in the 2022.2 line

 

Yes, indeed.

My comment was directed to @Nayjest , that instead of downgrading to 2021.x, he could downgrade just to 2022.1 (assuming he is not dealing with other issues).

 

They've at least acknowledged the issue and seem to be working on it now:
Unity Issue Tracker - Cannot archive build for iOS using Xcode 13.3 when the project is built on a Windows machine (unity3d.com)

The status of my ticket has moved to 'in progress' and fix pending review.

 

I really hope they will focus on this issue
In the meanwhile i'm just downloading the just released 2022.2.13f1 build to verify the bug state
but as there's nothing in the changelog, i'm pretty confident that nothing is fixed in that release

On top of that, our gitlab based CI/CD pipeline that uses unity docker images is stuck too on 2022.1 , as there is another problem caused by the unity hub. Apparently the latest 3.4.1 hub version fails to install the fitting JDK version( 2022.2 requires a newer JDK for Android builds )
At least that's what the docker guys say. So android builds fail in the gitlab CI/CD with 2022.2.
This is supposed to be fixed with the 3.5 HUB release, but my question in the hub forum, about a possible release date for 3.5 was left unanswered and without any response...

 

Tested recent 2022.2.13f1 release , no change, issue still exists...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

 

Just tested hot-off-the-press Unity 2022.2.14f1 release , no change, issue still exists...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

On top of that, since 2022.2.13f1i now get some AR related xassets compile error on iOS
As far i have seen this was already confirmed somewhere on the ARKit forum
https://forum.unity.com/threads/xr-...-is-not-added-to-xcode-project.1418527/unread

 

i have the same issue with Unity 2022.2.14f1

 

For completeness:
Unity 2022.2.15f1 release , no change, issue still exists...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

 

Barbie Q, because of this reason, our project will be in breach of contract... Now there are a lot of things that need to be changed in the reduced version, the contract will still be broken, please ask the official help

 

How did that happen? Just use the regex postprocessor and everything builds fine. Its not an elegant solution, but it works and shouldn't be a reason why you breach any contract.

 

Welcome to Groundhog Day ...

Unity 2022.2.16f1 release , no change, issue still exists...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

On top of that, the following AR related xassets compile error on iOS is still there
https://forum.unity.com/threads/xr-...-is-not-added-to-xcode-project.1418527/unread

 

While this is an extremely annoying problem, its not show-stopping and it also doesn't prevent publishing on iOS. Using the workaround in this thread resolves the issue and allows publishing just fine, we've done so multiple times already.

I get the frustration and I agree that it is a real issue though.

 

Welcome to Groundhog Week ...
According to my tests, nothing has changed with the recent 2022.2.17f1 release

Unity 2022.2.17f1 release , no change, issue still exists...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

On top of that, the following AR related xassets compile error on iOS is still there
https://forum.unity.com/threads/xr-...-is-not-added-to-xcode-project.1418527/unread

 

Another Groundhog Week ...
According to my tests, 2022.2.18f1 did not change in regards to the main issue...

Unity 2022.2.18f1 release ,ios path issue still exists...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

Apparently the other xassets has been fixed (tested only once )
https://forum.unity.com/threads/xr-...-is-not-added-to-xcode-project.1418527/unread

 

No surprise for us, same error with the recent 2022.2.19f1 release

Unity 2022.2.19f1 release, ios path issue still exists...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

 

Is there a workaround for TvOS as well?

Edit: for TvOS:

Code (CSharp):

1. mkdir -p "$CONFIGURATION_TEMP_DIR/artifacts/arm64/buildstate/"
2. ln -sF "$PROJECT_DIR/Il2CppOutputProject" "$CONFIGURATION_TEMP_DIR/artifacts/arm64/buildstate"
3. ln -sF "$PROJECT_DIR/Libraries" "$CONFIGURATION_TEMP_DIR/artifacts/arm64/buildstate"
4. HOST_ARCH=$(uname -m)
5. IL2CPP_DIR="$CONFIGURATION_TEMP_DIR/artifacts/arm64/buildstate/Il2CppOutputProject/IL2CPP/build/deploy_$HOST_ARCH"
6. IL2CPP="$IL2CPP_DIR/il2cpp"
7. chmod +x "$IL2CPP"
8. chmod +x "$IL2CPP-compile"
9. if [ "$HOST_ARCH" = "arm64" ];
10. then
11.     HOST_ARCH_BEE="arm64"
12. else
13.     HOST_ARCH_BEE="x64"
14. fi
15. chmod +x "$IL2CPP_DIR/bee_backend/mac-$HOST_ARCH_BEE/bee_backend"
16. if [ "$CONFIGURATION" = "Debug" ];
17. then
18.     IL2CPP_CONFIG="Debug"
19. else
20.     IL2CPP_CONFIG="Release"
21. fi
22. "$IL2CPP" --compile-cpp --platform=AppleTV --baselib-directory="Libraries" --incremental-g-c-time-slice=3 --dotnetprofile=unityaot-macos --profiler-report --print-command-line --static-lib-il2-cpp --generatedcppdir="Il2CppOutputProject/Source/il2cppOutput" --custom-il2-cpp-root="Il2CppOutputProject/IL2CPP" --architecture=arm64 --outputpath="$CONFIGURATION_BUILD_DIR/libGameAssembly.a" --cachedirectory="$CONFIGURATION_TEMP_DIR/artifacts/arm64" --configuration="$IL2CPP_CONFIG"
23.  

 

And another Groundhog Week round: Same error with the recent 2022.2.20f1 release.
Nothing has changed regarding the path error bug - no surprise for us.
I start to wonder whether "they" will let this slip into the 2022.3 LTS version release, which is expected to be launched somewhen in the near future

So to sum it up:

Unity 2022.2.20f1 release, ios path issue still exists...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

 

I vote for spacefrog as the newest Unity employee

 

To paraphrase @spacefrog :

Unity 2022.2.21f1 release, ios path issue still exists...

When is this due to be resolved @PavelLU ?

 

Hmm ... i guess he isnt with Unity any longer

 

Perhaps @JoshPeterson or @andyb-unity can shed some light!

 

As i have expected, they simply let the path bug when exporting to iOS from windows slip into the final LTS version...
sigh ... So i'll keep on posting

And another Groundhog Week round: Same error with the recent 2022.3.0f1 LTS release.
Nothing has changed regarding the path error bug - no surprise for us.
So to sum it up:

Unity 2022.3.0f1 LTS release, ios path issue still exists...
Postbuild processor regex fix is STILL required when exporting an iOS build on windows

 

Setting the "data-folder" worked, thank you so much!

 

Code (CSharp):

1. public class IOSPostProcessBuild
2. {
3.     [PostProcessBuild]
4.     public static void EditProject(BuildTarget buildTarget, string pathToBuiltProject)
5.     {
6.         if (buildTarget != BuildTarget.iOS)
7.             return;
8.  
9.         var projectPath = Path.Combine(pathToBuiltProject, "Unity-iPhone.xcodeproj", "project.pbxproj");
10.  
11.         var pbxProject = new PBXProject();
12.         pbxProject.ReadFromFile(projectPath);
13.  
14.         var targetGuid = pbxProject.TargetGuidByName("GameAssembly");
15.         var buildPhases = pbxProject.GetAllBuildPhasesForTarget(targetGuid);
16.  
17.         var phaseGuid = buildPhases.FirstOrDefault(x => pbxProject.GetBuildPhaseType(x) == "PBXShellScriptBuildPhase");
18.  
19.         var buildSectionAny = pbxProject.GetType().GetMethod("BuildSectionAny", BindingFlags.Instance | BindingFlags.NonPublic, null, new[] { typeof(string) }, null);
20.         var fileGUIDListBase = buildSectionAny.Invoke(pbxProject, new object[] { phaseGuid });
21.  
22.         var fieldInfo = fileGUIDListBase.GetType().GetField("shellScript", BindingFlags.Instance | BindingFlags.Public);
23.  
24.         var shellScript = (string)fieldInfo.GetValue(fileGUIDListBase);
25.  
26.         shellScript = Regex.Replace(shellScript, @"--data-folder=\""(.*?)\""", @"--data-folder=""$PROJECT_DIR/Data/Managed""");
27.  
28.        fieldInfo.SetValue(fileGUIDListBase, shellScript);
29.  
30.        pbxProject.WriteToFile(projectPath);
31.    }
32. }

Here's how I fixed it. Hope this helps somebody.

 

My ticket for this issue was updated the other day:
Unity Bug Reporting Portal
Yesterday 1:51 PM

A fix for your bug report IN-25375: Cannot archive build for iOS using Xcode 13.3 when the project is built on a Windows machine has been verified and approved.

Fix Version/s: 2022.3.2f1

Looks like a fix is on the way boys

 

False alarm boys

Unity Bug Reporting Portal
Yesterday 10:17 AM

The internal verification for IN-25375: Cannot archive build for iOS using Xcode 13.3 when the project is built on a Windows machine against ** has failed our internal review.

The request has been reopened and is awaiting further action.

 

I don’t know why you are all waiting faster turnaround times. Unity typically takes 6 months+ to fix issues like this one and this has been the case for a while now. If there is a workaround, use it and move on.

 

You saved my day!

 

Good news guys !
Apparently the path error bug when exporting an iOS build from Windows has been fixed !
My project exports correctly now on windows with Unity 2022.3.2f1 release and builds fine on Xcode without the regex fix in place!
Can anyone else who had this problem verify that ?
I still do not fully trust it , but things looking good !!

 

When trying to build a project without a fix script:

In my case, the script is still needed.
Unity 2022.3.2f1

 

this seems to be the bitcode thing, not the path error which requires the regex fix because the windows editor writes a hardcoded absolut windows path into the project (which of course doesnt work on a mac)
Again, seems to be the other problem

 

Apparently yes, it's just that my script fixes several problems at once. If it is useful to someone, then here is the part of the code responsible for Bitcode:

Code (CSharp):

1.         //ENABLE BITCODE FALSE FIX
2.         var pbxProject = new PBXProject();
3.         pbxProject.ReadFromFile(projectPath);
4.         foreach (var targetGuid in new[] { pbxProject.GetUnityMainTargetGuid(), pbxProject.GetUnityFrameworkTargetGuid() })
5.         {
6.             pbxProject.SetBuildProperty(targetGuid, "ENABLE_BITCODE", "NO");
7.         }

 

So can this just be stuck directly into the assets folder, and the script can be called anything? ...and its a regular .cs script?

 

Here is the full script, you can cut out the extra part. The script must be placed in the Editor folder.

Code (CSharp):

1. using System.IO;
2. using System.Text.RegularExpressions;
3. using UnityEditor;
4. using UnityEditor.Callbacks;
5. using UnityEditor.iOS.Xcode;
6. using UnityEditor.SearchService;
7.  
8. public class MyBuildPostprocessor
9. {
10.     [PostProcessBuild(999)]
11.     public static void OnPostProcessBuild(BuildTarget buildTarget, string path)
12.     {
13.         if (buildTarget != BuildTarget.iOS)
14.             return;
15.         var projectPath = path + "/Unity-iPhone.xcodeproj/project.pbxproj";
16.         //UNITY 2022.2.X FIX https://forum.unity.com/threads/xcode-build-error-after-upgrading-to-2022-2-0.1371966/
17.         var projRaw = File.ReadAllText(projectPath);
18.         projRaw = projRaw.Replace("chmod +x \\\"$IL2CPP\\\"",
19.             "chmod -R +x *\\nchmod +x \\\"$IL2CPP\\\"");
20.         projRaw = Regex.Replace(projRaw, "--data-folder=\\\\\"([^\"]*)\\\\\"",
21.             "--data-folder=\\\"$PROJECT_DIR/Data/Managed\\\"");
22.         File.WriteAllText(projectPath, projRaw);
23.  
24.         //ENABLE BITCODE FALSE FIX
25.         var pbxProject = new PBXProject();
26.         pbxProject.ReadFromFile(projectPath);
27.         foreach (var targetGuid in new[] { pbxProject.GetUnityMainTargetGuid(), pbxProject.GetUnityFrameworkTargetGuid() })
28.         {
29.             pbxProject.SetBuildProperty(targetGuid, "ENABLE_BITCODE", "NO");
30.         }
31.  
32.         //FIX SWIFT
33.         string mainTargetGuid = pbxProject.GetUnityMainTargetGuid();
34.         foreach (var targetGuid in new[] { mainTargetGuid, pbxProject.GetUnityFrameworkTargetGuid() })
35.         {
36.             pbxProject.SetBuildProperty(targetGuid, "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES", "NO");
37.         }
38.         pbxProject.SetBuildProperty(mainTargetGuid, "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES", "YES");
39.  
40.         pbxProject.WriteToFile(projectPath);
41.     }
42. }

 

I'm trying to compile for iOS with latest Unity 2022.3 lts from my Mac (Apple Silicon) with Xcode 15 beta6 and I'm getting this, any ideas?

 

I get the same (NEW) problem when using Xcode 15 beta 6. I think its the new xcode beta 6.
No problems when using Beta 5 so i reverted back to that version

Of course if its not actually an xcode bug but caused by upcoming changes in xcode, Unity should fix that