Skip to main content
July 31, 2024
Question

Mobile Safari Extension does no longer load after updating to app version 8.10.38

  • July 31, 2024
  • 17 replies
  • 463 views

Hi there,
after installing beta version 8.10.38, the Safari extension does no longer load when Safari has been force-quit. This might also happen when Safari is paused by iOS, but this of course harder to reproduce. However this problem does appear when force-quitting the app

Steps to reproduce:
1. Force-Quit Safari
2. Go to a webpage's login form you have stored a login item for
3. When tapping on the login field, the inline 1P menu is not displayed
4. Also going to the extension menu (puzzle icon) in the address bar and selecting on 1Password does not do anything
5. If you go to "Manage Extensions" and disable and re-enable 1Password, the extension does load again. But that is only until you force-quit Safari again.

Can anybody else reproduce this problem?


1Password Version: 8.10.38 (81038029)
Extension Version: 2.26.1
OS Version: iOS 17.5.1
Browser: Safari

17 replies

1P_Dave
1Password Employee
July 31, 2024

Hello @Manaburner! 👋

Thank you for the report! So that I can investigate this further, I'd like to ask you to reproduce the issue again and then create a diagnostics report from your iOS device:

Sending Diagnostics Reports (iOS)

Attach the diagnostics to an email message addressed to support+forum@1password.com.

With your email please include:

Please send the entire file.

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

-Dave

July 31, 2024

Hi @1P_Dave
the support ID number is BTG-47655-638

1P_Dave
1Password Employee
July 31, 2024

@Manaburner

Thank you for sending in the diagnostics report! One of my colleagues will reach out to you soon via email, please continue the conversation there.

-Dave

ref: BTG-47655-638

August 6, 2024

I have also been having this issue with multiple devices for several weeks.

It seems to be related to the “share across devices” functionality in iOS. If I disable and re-enable the extension on one device, it fixes it for that device but breaks it on all of the others connected to my Apple ID.

All of the devices are on iOS/iPadOS 17.6 and running 1P 8.10.38 right now.

August 6, 2024

I'm experiencing the same issues, will send in a diagnostic report.

August 10, 2024

Any progress on this? I’m having the same issue as well.

August 12, 2024

And me, same software versions as OP. Problem also arises after phone shutdown and restart.

1P_Dave
1Password Employee
August 16, 2024

@1bvr, @softleaf, @Tycho, and @theengine

I'm sorry that you're all running into issues with 1Password in Safari on your iOS devices. Please try the following:

  1. Update iOS to the latest version (17.6.1 at the time of writing).
  2. Force quit Safari from the App Switcher: Quit and reopen an app on iPhone - Apple Support (CA)
  3. Open your iOS Settings and go to Safari > Extensions > 1Password.
  4. Disable the setting for Allow Extension, wait a few seconds, and then re-enable it.
  5. Re-open Safari.

If you run into the same issue again after trying these steps then I'd like to ask you to create a diagnostics report from your iOS device:

Sending Diagnostics Reports (iOS)

Attach the diagnostics to an email message addressed to support+forum@1password.com.

With your email please include:

Please send the entire file.

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

-Dave

August 16, 2024

Hi, followed your suggestions and while it worked initially after closing safari or restarting the phone the same issue appeared.

Diagnostic Report sent: ticket number:
Your support ticket ID is MVU-93188-229.

Cheers,

August 17, 2024

Hi @1P_Dave. I encountered the issue again today despite having Share Across Devices disabled now. It seemed to help for a few days.

The steps you provided are the workaround I’ve been using to get the extension working again, but it is a frequent occurrence. I had to do the workaround steps to get into the extension in order to generate the diagnostic file, but there is no General tab in the extension settings (step 3).