Wifi Sync not working iOS 8.2 + OS X 10.10.2

hataewon
hataewon
Community Member

Since I updated the iOS to 8.2, the Wifi sync does not work anymore. I tried to turn on and off the sync on both sides, i.e. iOS and OS X, but it does not help. The 1Password iOS seems to have problems to find the server on OS X.

Comments

  • hataewon
    hataewon
    Community Member

    Solved, by rebooting both machines. But still very odd...

  • Hi @hataewon,

    Glad to hear you were able to get this fixed up.

    But still very odd...

    Agreed! If it pops up again please do let us know.

  • hataewon
    hataewon
    Community Member

    It popped again. The error message is: Computer not found. They are on the same WiFi network and as of today I'm running all the newest versions (OS X, iOS, 1Password on OS X and iOS).

  • Stephen_C
    Stephen_C
    Community Member

    I'm effectively running the same versions as you (save that I'm running the 1P for Mac beta) and from time to time experience the same problem with wifi sync. I suspect some sort of DNS issues still in OS X and/or iOS. Only yesterday my iPhone sync'd perfectly but my iPad simply refused in spite of repeated attempts, disabling wifi sync on it and the Mac then re-enabling, etc. Eventually I solved the problem by re-booting both the iPad and the Mac.

    Sorry, this is really a rather long-winded way of saying:

    1. you are not alone; and
    2. reboots do usually seem to solve the problem (until it re-occurs, of course).

    Stephen

  • Calvir
    Calvir
    Community Member

    Confirmed. Reboot of both devices required. Same scenario and versions.

  • There are still name resolution issues, at least in OS X 10.10.2. I have noticed occasionally my Mac will rename itself to "Ben's MacBook (2)" or "Ben's MacBook (3)" (etc) indicating it thinks there is a naming conflict on the network... Though there isn't. It appears Apple still has some work to do in this area.

  • hataewon
    hataewon
    Community Member

    Well, at least in my case it's not the name resolution issue. The hostname of my Mac does not change and I know this because for example I see that in my terminal prompt when that happens (yes, new terminal windows). Interestingly on the iPad I don't have this problem (same iOS and 1Password version). It worked well on 10.10.1 or older version of 1Password, I'm not sure which.

    This is very annoying.

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited March 2015

    @hataewon: I hear you! I wonder if this is related to a deeper wifi issue in Yosemite or iOS 8.

    While I haven't had a great deal of trouble with wifi specifically on iOS 8 (plenty of other strange behaviour there for me unfortunately, though), the wifi on my Yosemite Macs seems to fail silently fairly regularly. When this happens, just turning wifi off and then back on after a few seconds gets it going right away, every time, so I would give that a try first if you encounter issues in the future. But, as always, we're here for you if you need us! :)

  • SJBell
    SJBell
    Community Member

    I'm glad to hear I'm not alone. I have the mac problem, but iOS 8.2 had cause a problem with any iOS to Yosemite sync. I only have to reboot iOS device. It occurs when I return to my network and shows I am on my network. I check airport utility on Mac shows everything good, as does a visual check of equipment. I check airport utility app on phone and it tells me none of the equipment is there despite showing I'm on my network.

  • hataewon
    hataewon
    Community Member

    @brenty: yes, 10.10.2 did not solve the WiFi-issue for me. However, When I try to manually sync by "Sync Now", the WiFi of my Mac is not dead. I can very well imagine that this is an issue hard to reproduce, but I hope that you'll find out the cause.

  • cacloutier
    cacloutier
    Community Member

    The automatic wifi syncing of 1Password between my iPad and my MacBook Pro stopped working when I did the latest updates. Reboot works, but this should not be necessary.

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited March 2015

    @SJBell: In your case, it sounds like it may be either the wifi on the iPhone or Airport router itself that may be the culprit, since everything 'appears' in order to the Mac. If the Mac is indeed able to access Airport Utility normally, use it to:
    1. restart your Airport router, and while you are waiting a few minutes for that to finish booting up,
    2. disable wifi on both the Mac and iPhone. Once the Airport router light is normal again (solid green is the default, I believe),
    3. turn the wifi on the Mac and iPhone back on.
    I have to do this occasionally myself, as resetting the connection fully resolves a lot of strange issues where network connections are timing out. That's no good for anyone. ;)

    @hataewon, @cacloutier: Try the above steps as well. In most cases, it isn't necessary to restart the router itself, only the wifi on each device (this can often save you the trouble of restarting the device, or router, completely, if it is just the networking that is failing). But when issues like this crop up with increasing frequency, it's time to restart that router as well. 1Password doesn't manage any of the wifi connectivity itself; the operating system on each device (including the router!) handles network connections. Very frustrating!

    If, even after the above steps, you're still experiencing connection problems, there may be a deeper OS or hardware issue, but we'll cross that bridge when we come to it. Please let me know your results -- especially if you get specific error messages. I hope this helps! :)

  • LarsE
    LarsE
    Community Member

    I had the same issue, 1Password stopped sync via WLAN 8 days agob on both iPhone 4s and iPad 2. I'm on iOS 8.2 and iMac is on most recent updates from the Appstore for OS X. Reboot of all devices including the router did help (reboot without rooter reboot did not work). I will monitor and report back, if the issue will reoccure

  • Thanks for the update! Glad to hear rebooting helped.

This discussion has been closed.