Mavericks and iTunes 11.1.2 Won't wifi sync iPhone

Awsome!

That looks like a very likely candidate for the cause.

I will check my console log for something similar when I get home (currently at work).

Hi lkrupp;

lkrupp wrote:

Allan Clark wrote:

So... AirportExtreme doesn't offer a way to check/enable/disable IPv6.

Try Internet -> Internet Options using Airport Utility 6.3.2

Fortunately, you've shown how to confirm IPv6 for the internet/WAN side. Unfortunately, I'm trying to confirm whether IPv6 is shared/passed/blocked/busted on the LAN side.

I'm bridged, but going out of bridge-mode, "Network Options" only discussed DHCP and NAT options, no IPv6. "Wireless Options" on the wireless side only talks about the radio transcievers.

I appreciate your help and effort, but it's a near-miss. Did you see anything else in there I missed? I'm using AU-6.3.2 as well.

FWIW, https://discussions.apple.com/thread/5543796?answerId=23804115022#23804115022 discussing that USB-tethered sync is failing when the IOS device's wifi is active.

Assuming it's the same issue, points to the IOS-side having problems. Or maybe we have two things 🙂

FWIW, my iPod is too old to upgrade to iOS7, so it is still running iOS6. But my iPad is running iOS7. The problem started affecting both devices at the same time.

Prior to the upgrade to Mavericks, both devices synced via WiFi without issues.

I can't recall if I synced the iPad via WiFi while it was post-iOS7, but pre-Mavericks.

I've confirmed that I have identical output in my console log:

com.apple.usbmuxd[29]: _SendAttachNotification Device xx:xx:xx:xx:xx:xx@fe80::xxxx:xxxx:xxxx:xxxx._apple-mobdev._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.

The next few lines that all apear related are:

MuxNetworkInitiateConnect Client 0x1002193d0-usbmuxd/NULL requesting attach to xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:62078 failed, could not begin background connection attempt: -1

com.apple.usbmuxd[29]: HandleUSBMuxConnect Client 0x1002193d0-usbmuxd/NULL MuxNetworkInitiateConnect failed

AMDeviceConnect (thread 0x103181000): Could not connect to lockdown port (62078) on device 50 - xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: 0xe8000084.

_AMDevicePreflightWorker (thread 0x103181000): Pair worker could not connect to lockdownd on device 50: 0xe8000084.

com.apple.usbmuxd[29]: HandleDeviceAttachHelperCallback preflighting failed for WiFi device 0x33-fe80::xx:xxxx:xxxx:xxxx:0: 0xe8000084. Ignoring device.

I've attached the log output to the bug report I submitted to Apple.

The directions below worked to get all my i-devices back to being recognized and syncing over wifi (Mavericks/iTunes 11.1.3). 😀 One additional step I added was in Airport Utility changed my internet options to Configure IPv6 from link-local only to "Automatically"...found in Internet Tab, select Internet Options...

From another discussion thread on the same topic:

RKCOJOHN

Folks, you could try this - it worked a charm (so far) for me.

Go into System Preferences / Network.

Choose your ethernet and/or wifi connection.

Go to "Advanced". If you're working on wifi settings, you'll need to pick the TCP/IP tab from the next window. If you're working on Ethernet settings, it should default to the TCP/IP tab.

If IPV6 is set to "off", change it to "Automatically" or put in "Manual" settings as you prefer. Apply the changes. Close iTunes & restart the Mac. Open iTunes once you're restarted and, if you're like me, your wifi sync devices will show up very quickly in the side bar.

Sync still seems to pause for a while on last step, but it has not yet failed on iPad, iPad 2, iPhone 3GS, 4S & 5.

Steve's earlier post led me down this path and prompted me to check this. I have a vague recollection that I forced IPV6 to "off" to overcome problems with prior upgrades to OS X and/or iTunes.

Hope your frustration comes to an end as, hopefully, mine has. I'm optimistic because I've been playing around for 2 days with variations of all the suggestions on this discussion. I'll post back if, as for some others, this fix only works temporarily. Good luck!

Thank you, thank you, thank you! Rebooting my router did the trick 🙂

Thank you for this suggestion ezmil. It worked perfectly. For everyone with this problem going into your network pane on your active connection and hitting advanced and turning IPv6 on to automatically instead of off (what mine was set to) fixed the problem. I did not have to restart iTunes or the computer for it to fix it. It worked itself out in about a minute or so. I did not have to modify any of my Airport router settings from link-local.

This problem was definitely a Mavericks issue though because I used iOS 7 for a while before upgrading to Mavericks. Wifi sync was working perfectly in 10.8 and stopped working immediately after upgrading to 10.9.

ezmil, nice summary; I would add: if choosing "Automatic", ensure something (like your router or IPv4 source) is offering IPv6 addresses.

Mine isn't -- but my OSX-10.9 isn't even ASKING

Do you think I have a chance of success if I drop it to link-level? The IPv6s would have to configure themselves. The backbone is a Cisco 8-port GB router, but the Actiontec that gives out DHCPv4 doesn't offer a configuration to activate IPv6.

Turning IPv6 on at the operating system was all that was needed for me. My Airport router is still distributing IP addresses using IPv4. Meaning I left IPv4 as using DHCP in the 10.9 network preferences.

To reitterate Amin_AA's observation:

Amin_AA wrote:

Can confirm that 7.0.4 seems to have fixed my problem permenantly. Having said that, I have also disabled the 5 Ghz network on my WiFi router, forcing both my Mac and iPhone 4S to conect at 2.4 Ghz. But I did that before 7.0.4 was avaiable and it didn't solve the problem of the iPhone not appearing in iTunes so I'm pretty sure it's down to the iOS update.

I think people are conflating two issues in this thread: the none appearanse of the iPhone button in iTunes (over WiFi) and the removal of local Calender and Contact Synching (iCloud only). These are two issues are not at all the same and should be discussed sepratly.

For those suffering and complaining about the removal of local Calendar and Contact syncing, PLEASE go to http://www.apple.com/feedback/macosx.html and tell Apple why you think this is a bad idea and why you want/need it back!

aps.

For those suffering and complaining about the removal of local Calendar and Contact syncing, PLEASE go to http://www.apple.com/feedback/macosx.html and tell Apple why you think this is a bad idea and why you want/need it back!

aps.

You know, we hand over our personal data to complete strangers every time we use a credit card, sign an agreement, shop at a retail store. And we think nothing of it. All this NSA stuff has pushed people such as yourself over the edge. Apple clearly states that they use 128 bit encryption both directions. They clearly state they have no access to your encrypted data. I would certainly be inclined to trust Apple more than some minimum wage clerk at a gas station. And I don't want your ilk interfering with my ability to sync to iCloud. Wacked out security concerns like this are a joke. I will certainly send feedback to Apple but it won't be to your liking I'm sure.

Well, that didn't last long. A couple of days after my original post about 7.0.4 fixing my issue, the iPhone disapearded from iTunes never to return again without a USB connectoion.

IPv6 has never been disabled on my Mac or netwrok so it can't be that. Pretty anoyed now that the issue isn't even acknowledged by Apple.

Amin_AA wrote:

Well, that didn't last long. A couple of days after my original post about 7.0.4 fixing my issue, the iPhone disapearded from iTunes never to return again without a USB connectoion.

Me, too. Infuriating.

If I remember correctly, you did multiple things (changed IPv6, and restarted your Mac).

If your problem is the same as mine, I think your restart is the only thing that did anything.

For me, after I restart, iTunes will detect my iOS devices with no problems. The problem starts once the machine goes to sleep. After it wakes up, it no longer detects any devices over Wi-Fi.

That might explain why it worked for you at first, but then stopped working (after enough time passed for your machine to sleep).