Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0x
Issue ID
872096
Regression
No
[Mono Runtime Upgrade] Project fails to build for iOS in XCode
1. What happened
The build is OK in Editor, but then fails to be deployed to device from Xcode.
Error is:
.../New Unity Project/ios1/Classes/Native/Bulk_System.Configuration_0.cpp:16022:84: No member named 'Configuration' in namespace 'il2cpp::icalls::System'
2. How we can reproduce it using the example you attached
- There's 'ios1' folder with the build inside the project folder
- Open with Xcode
- Deploy to device (I'm using iPad2 for the purpose)
--->
'Build Failed' with:
.../New Unity Project/ios1/Classes/Native/Bulk_System.Configuration_0.cpp:16022:84: No member named 'Configuration' in namespace 'il2cpp::icalls::System'
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
- "SupportsRandomWriteOnRenderTextureFormat()" shows "False" when executed on 2023.2 and 6000.0 streams
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
mcarriere
Nov 08, 2017 17:04
And finally, resolution: there were some changes in the pbxproj file from 5.6 to 2017.2.0p1 that were creating this issue. After duplicating the compiler defines that the Unity build process kicks out into our pbxproj file, compilation was able to succeed.
mcarriere
Nov 07, 2017 13:55
Sorry -- I'd like to provide an update: this seems to be fixed if we build exclusively with the project that Unity spits out. We have a special build process that augments the Xcode project, and it seems like something has been added or changed to the Xcode project since 5.6.3 (the version we're upgrading from) that we will need to hunt down and replicate in our custom Xcode project.
For what it's worth: we're also using Vuforia.
I'll update a third time once I have more information on what we needed to do to make this work.
mcarriere
Nov 07, 2017 12:10
This is still occurring in 2017.2.0p1