Closed eyJhb closed 1 week ago
This is what we experienced with 1.0.151 and later. @dmissmann could you please look at it and see if #506 might introduce it?
This is what we experienced with 1.0.151 and later. @dmissmann could you please look at it and see if #506 might introduce it?
I did a git bisect, and it came back to that exact commit. So maybe I should have been more accurate in my wording. it IS that PR that caused it :)
I was also able to reproduce it on that version, but it puzzles me what went wrong there, apart from passing the device version around, that https://github.com/danielpaulus/go-ios/pull/506/files#diff-e348e1ae1ad9e1ba778331d17a3d441b29d905189a3ade020a763f9b75d9f0e9R124-R128 should be the only change, and for iOS 16 the value is identical to what was there before 🤯 I'll have another look tomorrow
I was also able to reproduce it on that version, but it puzzles me what went wrong there, apart from passing the device version around, that https://github.com/danielpaulus/go-ios/pull/506/files#diff-e348e1ae1ad9e1ba778331d17a3d441b29d905189a3ade020a763f9b75d9f0e9R124-R128 should be the only change, and for iOS 16 the value is identical to what was there before 🤯 I'll have another look tomorrow
Waiting good news 👍
I'll test the new release tomorrow at work :) Thanks!
Describe the bug Using
go-ios runwda
, it will just hang forever and not show the webdriveragent running.To Reproduce
go-ios image auto
go-ios runwda
Expected behavior I expect it to show the "webdriver agent running" message, but instead it doesn't show up, and the command just hangs with no progress.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context It seems to work just fine an v1.0.150, but not v1.0.151 (or latest commit), I suspect that #506 broke it, but I'm not entirely sure why. @dmissmann do you have any ideas?
Logs