Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
1
Found in
2018.2.0b1
Issue ID
1176139
Regression
No
[iOS] `Swift Language Version` is not set in Xcode Build Settings when a .swift source plugin is added to an Unity Project
To Reproduce:
1. Add a valid .swift source file to your Unity project and mark it as an iOS plugin.
2. Export and Xcode project and build it.
3. Observe that Xcode fails with:
The target "Unity-iPhone" contains source code developed with Swift 3.x. This version of Xcode does not support building or migrating Swift 3.x targets.
(or something similar)
This happens because we don't set the "Swift Language Version" (SWIFT_VERSION)" field to any Swift version in our build post-processor.
Tested on:
2019.1
2019.3
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceException is thrown when adding a Blur Renderer Feature
- [Linux] Dropdown Menus are filled with empty entries when the Menu intersects with the Editors borders
- [HDRP] [Metal] Tiled artefacts when using DRS
- [HDRP] Empty template starts with incorrect Physically Based Sky ground
- Big chunk of "Untracked" memory in the Memory Profiler screenshot when a custom .obj file is loaded while in Play Mode
tonythedad
Jul 19, 2020 23:23
Never been fixed for me it months.
Build target UnityFramework of project Unity-iPhone with configuration ReleaseForRunning
error: Invalid SWIFT_VERSION: Could not parse version component from: '0 5' (in target 'UnityFramework' from project 'Unity-iPhone')
Xcode 11.6
Unity 2019.4.2f1
Lex3425
Apr 25, 2020 19:14
I've come to experience the problem in 2019.3.5.f1 also. However, it seems like it has been fixed now. Errors like these are not massive but can be frustrating and are what we look to avoid on any of our websites like https://www.airbnbcleaningserviceanchorage.com. Glad to see this has been addressed and fixed.
rendermouse
Mar 16, 2020 14:19
I am experiencing this on 2019.3.5.f1 as well.
excalith
Feb 22, 2020 10:51
Still broken on 2019.3.1f1 and 2019.3.2f2. Used to build with 2019.3.1f1 but started to fail. Seems like something is breaking this