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

iOS 17 support #853

Open
Schlaubischlump opened this issue Oct 28, 2023 · 16 comments
Open

iOS 17 support #853

Schlaubischlump opened this issue Oct 28, 2023 · 16 comments

Comments

@Schlaubischlump
Copy link

Description

Since iOS 17 Apple changed how the developer functions, such as taking a screenshot, launching apps and location simulation are accessed. IDB currently doesn't seem to support these changes.

Reproduction

Try to use any of the functions mentioned above on an iOS 17 device.

Solution

To my knowledge two steps are required to support iOS 17.

  1. IDB must support mounting personalized developer disk images on iOS devices.
  2. IDB must use CoreDevice instead of MobileDevice to access developer functionality on iOS 17.

Additional Information

Are there any plans to support iOS 17 ?

@baptiste-faure1811
Copy link

+1

@KishanDasani
Copy link

we're stuck because of the same issue.

@FGandolfi
Copy link

+1

4 similar comments
@yuanjifeng
Copy link

+1

@bunyodrafikov
Copy link

+1

@JackSmerdon
Copy link

+1

@baptiste-faure1811
Copy link

+1

@stoefln
Copy link

stoefln commented Dec 4, 2023

Is this about following error? I am seeing this since I upgraded my iPhone to iOS 17:

The best match /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/16.1/DeveloperDiskImage.dmg: 16.1 is not suitable for 17.1
 (quit with code 1)
Error occued while executing command  "idb launch --udid 00008030-0010552A1E7A802E my.xyz.film-o-matic"

@bunyodrafikov
Copy link

Is this about following error? I am seeing this since I upgraded my iPhone to iOS 17:

The best match /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/16.1/DeveloperDiskImage.dmg: 16.1 is not suitable for 17.1
 (quit with code 1)
Error occued while executing command  "idb launch --udid 00008030-0010552A1E7A802E my.xyz.film-o-matic"

Yes, it is

@boraerbas
Copy link

+1

@Upcasting
Copy link

is there any solution? still faceing the same problem

@stoefln
Copy link

stoefln commented Feb 5, 2024

There has been a fix for this issue, however it doesn't seem to have found it's way into a release yet:
0d44466

We managed to compile the project, but we are not sure how to tell the python idb client to use the freshly compiled idb-companion binary.
Any ideas out there? Couldn't find any documentation on it.

@ellishg
Copy link

ellishg commented Feb 7, 2024

It seems that idb launch and idb install don't work on iOS 17 devices. Luckily, xcrun devicectl does work on iOS 17 and it has launch and install commands.

xcrun devicectl device process launch --device <udid> com.apple.camera

@fatahillahardhi
Copy link

Hi @ellishg thank you it really works! By the way, do you know how to terminate apps using devicectl?

@stoefln
Copy link

stoefln commented Feb 26, 2024

@fatahillahardhi there is a way, but you need to first figure out the process ID of the running process.
Here is an implementation that does that: https://github.com/appium/appium-xcuitest-driver/pull/1997/files#diff-bb0c8b8277b395d5bb9d3326ef4bacc41134fe47236c6e883d6ef720ef3d7195R231

@mroreo1
Copy link

mroreo1 commented Mar 25, 2024

Does currently IDB supports ios 17+ ios

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

No branches or pull requests