You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Target device model and iOS version. 17.4.1 (and apparently above)
iTunes is installed
Describe the bug
Developer commands ("developer dvt proclist" for example) that did work on a Win10 workstation are not working on a Win11 workstation. Typically I use --udid but that elicits an error:
"024-10-30 14:22:04 SEA1-PC-... main[40316] WARNING Got an InvalidServiceError. Trying again over tunneld since it is a developer command". But no response from the re-try over tunneld.
Re-trying manually using the --rsd option works as normal. A seperate issue is getting the rsd ID from an elevated cmd window running "UseShellExecute" - no redirect to a file.
To Reproduce
Run tunneld command
Run specific developer commands using the --udid option
Expected behavior
Commands work as expected on Win11
Logs
Additional context
For community
⬇️ Please click the 👍 reaction instead of leaving a +1 or 👍 comment
The text was updated successfully, but these errors were encountered:
Test environment
Describe the bug
Developer commands ("developer dvt proclist" for example) that did work on a Win10 workstation are not working on a Win11 workstation. Typically I use --udid but that elicits an error:
"024-10-30 14:22:04 SEA1-PC-... main[40316] WARNING Got an InvalidServiceError. Trying again over tunneld since it is a developer command". But no response from the re-try over tunneld.
Re-trying manually using the --rsd option works as normal. A seperate issue is getting the rsd ID from an elevated cmd window running "UseShellExecute" - no redirect to a file.
To Reproduce
Run tunneld command
Run specific developer commands using the --udid option
Expected behavior
Commands work as expected on Win11
Logs
Additional context
For community
⬇️ Please click the 👍 reaction instead of leaving a
+1
or 👍 commentThe text was updated successfully, but these errors were encountered: