Search Issue Tracker
Fixed
Fixed in 2022.3.66f1, 6000.0.56f1, 6000.1.16f1, 6000.2.1f1, 6000.3.0a4
Votes
0
Found in
2022.3.63f1
6000.0.50f1
6000.1.6f1
6000.2.0b4
6000.3.0a2
7000.0.0a35
Issue ID
UUM-108336
Regression
Yes
[iOS] Exported Xcode "Unity-iPhone" Xcode project shows the "Framework" folder as red
How to reproduce:
1. Create an empty project
2. Build for iOS
3. Open the “Unity-iPhone.xcodeproj“
4. Observe the “Frameworks“ folder
Expected result: The “Frameworks” folder is not red
Actual result: The “Frameworks” folder is red
Reproducible with: 2022.3.55f1, 2022.3.63f1, 6000.0.50f1, 6000.1.6f1, 6000.2.0b4
Not reproducible with: 2022.3.0b1 (ea0f0219deed), 2022.3.54f1
Reproducible environment: macOS 15.4.1 (M4 Max)
Not reproducible environment: No other environment tested
Notes:
- Tested with Xcode versions 16.2 and 16.3
- This does not prevent from building an iOS app
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 6000.3.0a4):
Fixed