Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use xcrun devicectl to deploy to iOS devices. #204

Closed
simlay opened this issue Jan 9, 2024 · 2 comments · Fixed by #215
Closed

Use xcrun devicectl to deploy to iOS devices. #204

simlay opened this issue Jan 9, 2024 · 2 comments · Fixed by #215

Comments

@simlay
Copy link
Contributor

simlay commented Jan 9, 2024

Looks like ios-deploy has issues with Xcode 15. ios-control/ios-deploy#588

Xcode 15 added a new tool xcrun devicectl which is similar to xcrun simctl but for physical devices. Though, it doesn't work with older devices - I've got an iphone 5 that doesn't list with xcrun devicectl list devices.

@kali
Copy link
Collaborator

kali commented Feb 22, 2024

I had a look, and this is a very sad mess. devicectl will just let us start the app. There is no way to capture output or the app return code. And it looks like the ios-deploy folks have more or less given up.

At this stage, I can't see any "clean" way out of this. Nothing that does not rely on super hacky stdout/stderr capture from within the app... or something else from within the app, like a custom test harness. And a way to gather all of this from the development host.

This is very sad. Apple has waited nearly 20 years to provide half of a solution to a problem they created, and managed to break the third-party solution doing so.

@kali
Copy link
Collaborator

kali commented Feb 22, 2024

There may be part of a solution here ios-control/ios-deploy#588 (comment)

Basically we would have to switch ios-deploy for https://github.com/doronz88/pymobiledevice3 and try to replug everything back together. And hope Apple does not break it again in three months...

@kali kali linked a pull request Feb 27, 2024 that will close this issue
@kali kali closed this as completed in #215 Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants