Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0a20
2022.1
Issue ID
1345172
Regression
No
[IOS] Both tethered and remote connection are showed in Profiler when the device is only tethered and WiFi is disabled
Steps to reproduce:
1. Create an empty project or open an existing one
2. Go to Build Settings and check Development Build (File -> Build Settings)
3. Build and deploy to a device with WiFi disabled
4. Open Profiler (Window -> Analysis -> Profiler)
5. Check the Target Selection dropdown
Expected result: Device only available in tethered devices
Actual result: Device available both in tethered and remote connections
Reproducible with: 2019.4.28f1, 2020.3.11f1, 2021.1.14f1, 2021.2.0b2, 2022.1.0a1
Notes:
- The new Target Selection dropdown look was introduced in 2021.2 and has named sections of Tethered and Remote, however, with the same steps you'd get two connections available in previous versions as well
- Doesn't repro on Android
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
- Unity crashes during the scene template selection in the "Inspector" tab
- [Android] [iOS] [UnityWebRequest] Requests with "UnityWebRequest" are open for SSL Proxying
- SetWindowsHookEx does not prevent Windows key input when Editor or Player Window is focused and Active Input Handling is set to “Input System Package (New)” or “Both”
- Crash on GetEffectiveBc7TextureCompressor() when loading and unloading all Assets in the Project
- Terrain Masks do not ignore the mipmap limit
Resolution Note (2022.1.X):
This is by design as apple maps usb to tcp so the running player will show up. The new connection dropdown just makes this more apparent. Previoius versions also showed the player and the device.