Bug 1382282 - iOS 10 devices no longer accessible
Summary: iOS 10 devices no longer accessible
Keywords:
Status: CLOSED DUPLICATE of bug 1387253
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libimobiledevice
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 08:52 UTC by Oliver Ilian
Modified: 2017-03-14 14:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-14 14:17:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
ipad connect logs (2.92 KB, text/plain)
2016-10-06 08:53 UTC, Oliver Ilian
no flags Details

Description Oliver Ilian 2016-10-06 08:52:52 UTC
Description of problem:
After upgrading a iOS device (iPhone or iPad) to iOS 10 , it is no longer possible to connect it.

Version-Release number of selected component (if applicable):
libimobiledevice-1.1.5-6.el7.x86_64
kernel-3.10.0-510.el7.x86_64

How reproducible:
Everytime you connect a iOS 10 device

Steps to Reproduce:
1. connect a iOS device via USB
2. Click trust on the Ipad and click "try again" on the screen to try to connect to the iPad again

Actual results:
iPad shows up in nautilus, however can not be accessed.

Expected results:
access to all files on the iPad

Additional info:
Attached is the log file from attaching the iPad on a Lenovo T430s and detaching it. 

the line:
Oct 06 10:51:11 ohaessle.muc.csb gpod[25962]: Client creation/handshake failed: -14

always appears and the dialog to say the iPad is locked appears even if the iPad is unlocked and it is only asked to trust the computer.

Comment 1 Oliver Ilian 2016-10-06 08:53:29 UTC
Created attachment 1207884 [details]
ipad connect logs

Comment 3 Robert Lightfoot 2016-10-22 19:34:24 UTC
libimobiledevice-1.2.0 apepars to resolve the IOS10 issue.

Comment 4 Oliver Ilian 2016-11-24 11:28:51 UTC
Is there a way to either backport this change, or make libimobiledevice-1.2.0 available in RHEL?

Comment 5 Oliver Ilian 2016-11-24 12:00:29 UTC
This are the packages that need to be updated for libimobiledevice-1.2.0

https://copr-be.cloud.fedoraproject.org/results/ohaessler/libimobiledevice-update-1.2/epel-7-x86_64/

Comment 6 Derek Atkins 2016-11-28 03:21:19 UTC
It's not solved in 1.2.0 -- it requires code newer than 1.2.0.  At least, I had this issue with FC23 and that distributes 1.2.0

c.f. https://github.com/libimobiledevice/libimobiledevice/issues/346
and https://github.com/libimobiledevice/ifuse/issues/32
and related bugs.

FWIW, I downloaded and installed the RPMs from https://github.com/RPM-Outpost/libimobiledevice (which, granted, are based on FC24 but installed without error on my FC23 system) and they fixed the problem (after I restarted usbmuxd).  This was from git HEAD as of 2016-11-04.

So you need something newer than 1.2.0 -- but there is no released version that fixes the problem, AFAICT.

Comment 7 Oliver Ilian 2016-12-02 13:44:35 UTC
If the fixes will be put into a release, is there a possibility to get this new version of libimobiledevice into RHEL 7?

Comment 8 Bastien Nocera 2017-03-14 14:17:15 UTC
Will be fixed by the rebase to a newer libimobiledevice.

*** This bug has been marked as a duplicate of bug 1387253 ***


Note You need to log in before you can comment on or make changes to this bug.