“Failed to copy” error on iOS

B9039
B9039
Community Member
in iOS

Hi there —

Ever since 1Password 8 was released I’ve noticed it being much more error prone than 1Password 7. Admittedly a restart of the device tends to fix things, but I often am in the middle of a jam packed day where I need a login to work, right at the start of a meeting — no time for a restart. I have a bit of time this week so wanted to send in some bug reports to try to get some help resolving them, and (hopefully) to help development address them more permanently.

This is one I regularly get — when trying to copy a field, I just get a “failed to copy” error in the browser extension. It happens on all fields sometimes (this screenshot happened to be when attempting to copy the one-time code from the Safari extension on iPad). It also happens on my Mac and my iPhone sometimes. I was trying to manually copy it because it wasn’t successfully autofilling in the browser, so I think there may have been an underlying issue causing both? Help?

Thanks for guidance, and hopefully, a permanent resolution to the underlying cause!

1Password Version: 1Password for iPadOS 8.10.34
Extension Version: Safari extension 2.23.3
OS Version: Not Provided
Browser: Safari

Comments

  • Dave_1P
    Dave_1P
    edited July 15

    Hello @"B"! 👋

    I'm sorry for the inconvenience. It sounds like you're running into a few known issues with 1Password for Safari on iOS. The following steps might help to temporarily resolve the issue and allow you to copy and paste from the extension:

    1. Open the Settings app.
    2. Tap Safari.
    3. Tap Extensions.
    4. Tap 1Password.
    5. Tap Other Websites.
    6. Tap/select Ask.
    7. Switch back to Safari (the app).
    8. Tap the aA / puzzle piece icon.
    9. Tap 1Password.
    10. Tap Allow.

    This is something that our developers are working with our friends at Apple to resolve and I'm told that the issue is fixed in the latest iOS 18 betas. Hopefully that fix will be released with iOS 18 later this year and resolve the issue permanently.

    -Dave

    ref: dev/core/core#9820