Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.4.X
Votes
2
Found in
2018.4.0f1
2019.2
2019.3
2019.3.0f3
2020.1
Issue ID
1216005
Regression
Yes
[iOS] "Append" is enabled when building an project targeting "Device SDK" on top of a project built for the "Simulator SDK"
How to reproduce:
1. Open the attached EmptyProject.zip project
2. Switch to iOS platform and Set iOS Target SDK to Simulator SDK
3. Build for iOS
4. Set iOS Target SDK to Device SDK
5. Build for iOS by leaving the same name and pressing "Append", deploy the Xcode project to the iOS device
Expected: Build succeeds
Actual: Build fails with a thrown error: /Users/vita/Downloads/case_1216005-EmptyProject/hgfd/Libraries/libiPhone-lib.dylib: No such file or directory (in target 'Unity-iPhone' from project 'Unity-iPhone') (see the full error in the Edit section)
Reproducible with: 2018.4.0f1, 2018.4.17f1, 2019.2.19f1, 2019.3.0f6, 2020.1.0a22
Not reproducible with: 2017.4.36f1
Regressed in: 2018.4.0f1
Note: The Xcode project is not updated correctly. This only happens when building Simulator first, then Device. It doesn't happen in the other direction
Comments (2)
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
- UI becomes unresponsive when using AppUI Navigation and Event System is attached
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
sandeepsmartest
Apr 13, 2020 12:44
Temporary fix: Replace the build instead of append
sandeepsmartest
Apr 13, 2020 12:37
Did anyone solve this??