Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.1f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1178009
Regression
No
[iOS] Visual Studio debugger doesn't find iOS player process after building app with Xcode
How to reproduce:
1. Open the "debug.zip" project
2. Open the NewBehaviourScript.cs in Visual Studio
3. Build the project for iOS
4. Make sure the iOS device and computer are connected to the same Wi-Fi hotspot
5. Build & Launch the app on a device
6. In Visual Studio, try to attach debugger to the device (Run > Attach To Process)
Actual result: There is no iOS Player process found in processes list.
Expected result: iOS Player process is found in processes list.
Reproducible with: 2020.1.0a2, 2019.3.0b2, 2019.2.4f1, 2018.4.8f1, 2017.4.32f1.
Devices reproducible with:
- iPhone 8 Plus (iOS 12.0)
- iPad Pro (according to user)
Devices not reproducible with:
- iPhone 6S Plus (iOS 10.3.2)
- iPhone 6S Plus (iOS 11.4.1)
- iPhone 6 (iOS 12.2)
- iPhone 7 Plus (iOS 12.0)
- iPhone 8 (iOS 12.3.1)
- iPhone 8 Plus (iOS 12.2)
- iPhone X (iOS 11.3.1)
- iPhone XR (iOS 12.0)
- iPhone XS Max (iOS 12.3.1)
- iPad (iOS 11.2.1)
- iPad 5th gen (iOS 10.3.3)
- iPad (iOS 11.0)
- iPad Mini 2 (iOS 11.4.1)
Notes:
- The process appears after the device is unplugged from Mac and the app is restarted.
- Profiler manages to find the player process.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This error happens on only a select few iOS version/device combinations. We won't plan to correct it, as updating to a newer iOS version corrects it.