GPS Rollover Nov 3, 2019 and 1Password - 32bit CPU Wi-fi + Cellular devices

wkleem
wkleem
Community Member
edited July 2019 in iOS

I am not certain how many here (presumably only a few - 32bit CPU devices only) will be affected but Apple has released a GPS Rollover Fix for iOS 10.3 and iOS 9.3. Wi-fi + Cellular models from 2012 and earlier are affected. 1Password requires the date and time, (also location?) to be correctly synced in order to work correctly?

https://support.apple.com/en-us/HT210239

Just an advanced warning. In spite of efforts with regard to the iOS10 to iOS11 upgrade, 32bit/64bit OS and CPU, some people were still unaware and were locked out of 1Password. IOS 11 was the first iOS to require a 64bit CPU.

https://discussions.agilebits.com/discussion/82810/old-version-of-1password-wont-open-legacy-32-bit-apps-cannot-run-on-ios-11-or-12/p2

If all else fails, 8 years (2020) is a Long time to have kept the old device. Time to get a new one.

Comments

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited July 2019

    Interesting. I hadn't heard of that one, but it shouldn't have any effect on people's ability to access their 1Password data, as that's neither tied to time nor requires an internet connection. Sync, TLS, and many other things that rely on the time may be affected, but the time can be set correctly in system settings manually if necessary...and, frankly, given that devices going back to the iPhone 4S and iPad 2 are getting an update for this, that should be more than sufficient; older devices will have many other issues regardless of this one (for example, the sync services that versions of 1Password for those devices used changed years ago). Cheers! :)

  • wkleem
    wkleem
    Community Member
    edited July 2019

    Just a concern. I and others had issues (mine was a different issue) with 1Password when a message appeared: Server's time may be out of sync. This was with Duo integration with 1Password. Things have improved since that time, over 2 years ago.

    https://discussions.agilebits.com/discussion/77925/entire-team-locked-out-the-servers-time-may-be-out-of-sync

    My own discussion on this topic of server's time may be out of sync is here:
    https://discussions.agilebits.com/discussion/77288/duo-and-1password-integration-issues/p1

    I am unaffected by the GPS rollout bug as my devices are on iOS 12 now.

    Unfor

    An update for anyone reading this in the future:

    (copied from my message on another thread)

    Unfortunately the other thread wasn't mentioned so it is hard to trace back to it

    In our last deploy we released a feature where disabling the Duo-1Password integration by deleting or changing API keys from Duo's administration panel will automatically disable the Duo integration on your 1Password account to prevent you from getting locked out. This can help restore access to your 1Password account due to any Duo-related problems, like local clocks being out of sync, or whatever the issue might be: you delete the integration from within Duo's admin panel and we will detect that and disable Duo from your account. Note that Duo is not disabled if we cannot reach Duo due to network errors, clock sync, or other problems, only in the cases of deleted integration, or resetting the Duo-1Password integration API keys.

    This can be a great way to disable Duo account protection in a lock-out situation.

    The GPS rollout issue won't affect anyone within 7 years to date from 2013 (iPhone 5s) to now.

  • AGAlumB
    AGAlumB
    1Password Alumni

    Ah gotcha. Yeah, that could cause some issues for Duo, but it's not supported on outdated OSes anyway, and the time can be set manually. The best thing to do, especially in the context of security, is stay up to date.

  • wkleem
    wkleem
    Community Member

    It's good to know that the GPS Rollover bug is an non issue then.

    To put some humour here, Ben's phone from the Bronze Age. :) Love that quote. Make sure that old phone is patched.

    https://discussions.agilebits.com/discussion/comment/516878#Comment_516878.

  • AGAlumB
    AGAlumB
    1Password Alumni

    Well, it does sound like it will be a pain for some number of people on an outdated OS/device (relatively small, percentage-wise, but probably still a substantial number of individuals), but won't affect 1Password directly at least. :)

    Also, I love that quote too. :lol:

  • wkleem
    wkleem
    Community Member

    Thanks! I am surprised at the device longevity out there and that Apple would actually fix the issue for old devices such as the iPhone 4s and iPad 4. That's it from me.

  • AGAlumB
    AGAlumB
    1Password Alumni

    That surprised me too. Good catch. :)

  • wkleem
    wkleem
    Community Member

    It's worse now for the iPhone 5.

    If users have not upgraded to iOS 10.3.4. by early November the App Store, email, GPS will be cut off. iPhone 5c is not mentioned but the 5c is just a 5 in different packaging? I imagine most 1Password users would have upgraded by now but number of those caught off guard by the 32bit to 64bit transition makes me wonder...

    https://9to5mac.com/2019/10/26/iphone-5-software-update-gps/

    "However, the problem is even more serious for iPhone 5. Apple is sending out alerts to iPhone 5 owners that their phones must be updated to iOS 10.3.4 before November 3. If the iPhone 5 is not updated in time, it will be unable to connect to the internet entirely, including web browsing in Safari, email, iCloud and App Store services.

    iPhone 5 owners are seeing this rather hilariously-tall dialog appear on their phones to make them aware of how critical doing the update is. Apple has also released a support document to explain the details further."

  • AGAlumB
    AGAlumB
    1Password Alumni

    I mean...the 64-bit transition was completed over two years ago with iOS 11. That and more recent versions do not support 32-bit at all. At this point the solution is really to upgrade to something newer, as this is just one of the issues facing outdated devices, and there will only be more over time.

This discussion has been closed.