Search Issue Tracker
Fixed in 2022.3.38f1
Fixed in 2022.3.X, 2023.3.X, 2023.3.0a11, future release
Votes
5
Found in
2021.3.17f1
2022.2.5f1
2023.1.0b4
2023.3.0a1
Issue ID
UUM-29212
Regression
No
Managed debugger does not work on iOS 16
Repro steps:
Follow the managed debugger instructions for either Visual Studio or Rider, using an iOS 16 device: [https://docs.unity3d.com/Manual/ManagedCodeDebugging.html]
(Run a debug build in airplane mode with script debugging enabled on the same network as the Editor)
Expected:
iOS device appears in the IDE's "Attach to Process" window, allowing you to attach and debug as expected.
Actual:
iOS 16 devices do not appear.
I have reproduced this issue as also noticed by users in the forums (scroll down to bottom of thread): [https://forum.unity.com/threads/cant-attach-visual-studio-to-ios-device.579565/]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
- Physics Debugger displays mouse cursor ray casts when Game view is not open if Input System package is used
Add comment