Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2017.4
2019.3
2019.3.5f1
2020.2
Issue ID
1237338
Regression
No
[macOS] [Xcode] Build & Run does not deploy the application to connected device automatically
1. Create a new project
2. Switch Platform to iOS
3. Connect an iOS device to your Mac
4. Build and Run
Expected result: Xcode is launched after Unity finishes building and the project is automatically Deployed to the connected iOS device (note 1)
Actual result: Xcode is launched, Indexing is completed and Xcode remains in a "Ready" state
Reproducible with: 2017.4.40f1, 2018.4.22f1, 2020.2.0a8
Reproducible with macOS 10.15.3 Catalina & Xcode Version 11.4 (11E146)
Not reproducible with macOS 10.15.2 Catalina & Xcode Version 11.4 (11E146)
Notes:
1. Sometimes Xcode is turned on and remains in the project selection screen for some time and during that time Unity is frozen. This resolves in ±30 seconds
2. Sometimes Unity has "Building Player" window at 100% progress
3. I was not able to test this with earlier Xcode versions and am not sure if this is a combination of macOS and Xcode or either of them separately
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.2):
Hub issue resolved in hub 2.3.1 which is available at https://unity3d.com/get-unity/download