Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.5.1p3
Issue ID
907857
Regression
Yes
[iOS] XML formatting error in Unity-iPhone XCode Scheme file
Steps to reproduce:
1. Create an empty project
2. Open Build settings
3. Change Build target to iOS
4. Build for iOS
5. When build completes, navigate to: "{BUILDPATH}\Unity-iPhone.xcodeproj\xcshareddata\xcschemes" and open Unity-iPhone.xcscheme file
Result: under <LaunchAction> tag, the last attribute "queueDebuggingEnabled" is not included to the tag, since a premature right bracket ">" appears after allowLocationSimulation attribute.
Expected result: queueDebuggingEnabled is included in <LaunchAction>
Reproduced with: 5.5.3p2, 5.6.0p4, 2017.1.0b4
Did not reproduce with: 5.3.7p2, 5.4.5p1
Note: "LaunchAction.png" attached to the case displays the issue visually
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment