Closed xkww3n closed 1 month ago
Wasn't able to reproduce. Try adding debug prints and see why it fails
how to fix https://stackoverflow.com/a/78460385
@AnNEDoMini I'm not familiar with the issue. If this is something you can reproduce, can you create a PR for it?
@AnNEDoMini I'm not familiar with the issue. If this is something you can reproduce, can you create a PR for it?
I did not dig it too far. Mostly because not all of the windows desktops are experiencing this bug. Like half of them, sometimes. But with such fix - works perfectly. Dunno, may be add some sort of a switch/envvar --use_selector_event_loop or USE_SELECTOR_EVENT_LOOP
I could just always do that on windows. Is there a downside to this? This sounds more like a Python bug
I could just always do that on windows. Is there a downside to this? This sounds more like a Python bug
Do not know any downsides, but as always it may lead to some wired interactions. Anyway, I'll add a PR with fix, add to readme(with clear statement "uses selector event loop..."); if anything goes wrong it is always possible to revert or improve solution.
Closing this now as I understand this is fixed. Feel free to reopen if needed
Test environment
Describe the bug Every
developer
command will fail withOSError: [WinError 1231]
error. I've trieddeveloper dvt sysmon system
,developer dvt ls /
anddeveloper dvt simulate-location set 0 0
, with or without--tunnel ''
argument.To Reproduce Steps to reproduce the behavior:
pymobiledevice3 usbmux list
, seen my device appeared.sudo pymobiledevice3 remote tunneld
.pymobiledevice3 developer dvt sysmon system --tunnel ''
in a new terminal window.OSError: [WinError 1231]
error. Expected behavior Commands should work.Logs
Additional context None
For community
⬇️ Please click the 👍 reaction instead of leaving a
+1
or 👍 comment