Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
5.1.0f3
2017.4.0f1
Issue ID
703217
Regression
No
[iOS] Framework Search Paths are overriden using Append
Reproduction steps:
1. Create a new Unity project.
2. Create and open the iOS Xcode project.
3. Go to the Xcode Build Settings (Unity-iPhone_xcodeproj.png).
4. Look for the "Framework Search Path" field (Unity-iPhone_xcodeproj.png).
5. Enter a custom value (e.g. "$(SRCROOT)/Frameworks").
6. Close the Xcode project.
7. Go to the Unity Editor, build an Xcode project on top of the old Xcode project and select 'Append'.
8. Repeat steps 3-4.
Actual behavior:
- "Framework Search Path" field is empty.
Expected behavior:
- "Framework Search Path" field has a previous value.
Reproduced with:
2017.4.18f1, 2019.1.0a13
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment