Xcode Legacy Build system is deprecated

When I open my Unity-generated project in Xcode, I get a bunch of warnings, including a message about the Legacy Build System being deprecated. I thought I'd try switching it to the New Build System, and it seemed to build OK, but the next time I went to build from Unity and chose "Append" I got an error about "Deletion of any of the unity targets is not supported". I can build fine with Replace and then it gets switched back to the Legacy Build System.

Is Unity going to generate projects with the New Build System selected soon?

 

+1 I am interested in this question.

Or is there a way to change this setting using
PostProcessBuildAttribute?

 

same question here, why is something like this not addressed anywhere?

 

You could make a post processing script edit this file after the xcode project is built out: YourProject.xcodeproj/project.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings, either edit a raw string or load the file with an XML parser, look for and remove this part ie. there's no setting to change the value of Original to something else, it's the lack of this value at all which will enable the project to use the new build system:

Code (CSharp):

1. <key>BuildSystemType</key>
2.     <string>Original</string>

 

Is there any indication from Unity if they expect to have any issues with the new xcode build system? like is there any reason to not use it??

 

Btw - anyone trying to find how to check or change the build system value in an Xcode project, look in File > Project Settings, or by clicking on the little orange hammer icon in the top middle of Xcode.

 

Some more info on the new build system differences here:
https://medium.com/xcblog/five-things-you-must-know-about-xcode-10-new-build-system-41676cd5fd6c

One of the differences to note is that the Run Script phase sounds like it's received a bunch of improvements and behavioural changes.

 

I've been building with the new system for a while there are no issues. I'm not sure why the project Unity creates doesn't default to it.

 

I've actually run into issue while was trying to make a [PostProcessBuild] script for this particular purpose.
Unity generates .xcodeproj but not the .xcworkspace file. Search says there is no entries of WorkspaceSettings.xcsettings in whole folder.

Good sir, could you please share your PostProcessBuild code snippet for that or pinpoint exact place of file?

 

Hi there, I've got my post process snippet in the following forum thread, but note that I've noticed recently that the workspace settings file is no longer being created as well. I don't know if this is because of an Xcode update, or because of a change to the Unity template that gets used to build out the xcode project. But in my case despite that settings file missing the project seems to be set to use the new default build system not the legacy one, so it doesn't seem to matter for me anymore. I can tell you that Unity changed the default setting to the new default as of 2020.3.10:
https://forum.unity.com/threads/202...sembly-run-script-build-phase-errors.1083767/

 

Hi Alexey,

With the new build system, what is the status of the xcframeworks support and how should they be imported in the plugins?
Can you elaborate more on this note from the release:

• iOS: Ignore plugins with wrong CPU type when creating xcode project, e.g. when building for run on device, libraries having CPU type "x64" (i.e. simulator libraries) will be ignored

I am trying to create a package which contains an xcframework. When imported, the aim is to be able to export for both device and simulator targets but currently fails with "Plugin is used from several locations", "Plugins colliding with each other."

Thanks!

 

I suggest you option which worked for me:
1. Open Xcode, goto project settings (click topmost icon in project navigator)
2. Go to "UnityFramework" target
3. Go to "Build Phases"
4. Expand "Link Binary with Libraries"
5. Delete both entries of *.framework BUT make sure *.xcframework is in there

This happens because Unity detects *.framework under Assets folders and sets default import settings. To avoid this just untick every goddamn checkbox (even iOS) for both entries of *.framework under .xcframework (which is treated as folder in Unity).

Hope it will help

 

Just an FYI, the Legacy Build Issue by default seems to have been resolved in 2021.2:
https://issuetracker.unity3d.com/is...de-build-fails-when-using-legacy-build-system

 

This doesn't seem to be the case in Unity 2020.3.7, which I am using right now and seeing this anytime I make a new build (not append).

 

It's very unfortunate when the response to Unity issues are "upgrade to the new version of Unity". Unity is so fragile, updating versions after a working app is completed has always lead to further issues and problems. I successfully deployed several versions of a mobile game to the Play and App Stores using Unity 2019.3.2f1. Updating the app to a newer build of Unity is not an option.

 

"new build system should be used on latest 2019/2020/2021"

Doesn't seem to be accurate, as 2019 is still causing this error.