idb icon indicating copy to clipboard operation
idb copied to clipboard

iOS 17 support

Open Schlaubischlump opened this issue 1 year ago • 16 comments

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 ?

Schlaubischlump avatar Oct 28 '23 21:10 Schlaubischlump

+1

baptiste-faure1811 avatar Nov 01 '23 23:11 baptiste-faure1811

we're stuck because of the same issue.

KishanDasani avatar Nov 02 '23 04:11 KishanDasani

+1

FGandolfi avatar Nov 13 '23 08:11 FGandolfi

+1

yuanjifeng avatar Nov 14 '23 00:11 yuanjifeng

+1

bunyodrafikov avatar Nov 15 '23 12:11 bunyodrafikov

+1

JackSmerdon avatar Nov 16 '23 15:11 JackSmerdon

+1

baptiste-faure1811 avatar Nov 17 '23 10:11 baptiste-faure1811

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"

stoefln avatar Dec 04 '23 14:12 stoefln

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

bunyodrafikov avatar Dec 04 '23 14:12 bunyodrafikov

+1

boraerbas avatar Dec 10 '23 13:12 boraerbas

is there any solution? still faceing the same problem

Upcasting avatar Jan 18 '24 06:01 Upcasting

There has been a fix for this issue, however it doesn't seem to have found it's way into a release yet: https://github.com/facebook/idb/commit/0d4446648ad4e1b8f4e462304fbb5a20c1608e8d

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.

stoefln avatar Feb 05 '24 08:02 stoefln

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

ellishg avatar Feb 07 '24 21:02 ellishg

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

fatahillahardhi avatar Feb 26 '24 09:02 fatahillahardhi

@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

stoefln avatar Feb 26 '24 09:02 stoefln

Does currently IDB supports ios 17+ ios

mroreo1 avatar Mar 25 '24 07:03 mroreo1