iPadOS 16.1 Watchtower crash [Fixed. Please see the approved answer for details.]

Hopefully it gets fixed one of these days because it is a very annoying bug…

I just signed up for 1password and am getting the same crash on my iPad when I enter watchtower. Once it crashes, it will not start again. If I wait a few hours or just uninstall/reinstall it will work again. It looks like you have a fix identified so I’m guessing you don’t need any diagnostics from me? If that is not correct and you do want diagnostics, please let me know.

@CMRater – Solved from our end! Hopefully the update will be made available without much delay. :)

@RonnyC – I hope so too! It's a showstopper for our customers and I want to see the fix in people's hands as soon as possible.

@BillL1 – The Watchtower tab is what causes this particular bug, so I'd suggest using it on another device (which will work just fine) or through 1Password.com if you need to use Watchtower. Our development team have already built the fix, so we're all good on the diagnostics front, but thanks for the offer!

OS: iPadOS 16.2
Device: iPad Mini 5th Gen
1Password: 8.9.7

The app crashes when tapping on Watchtower/Compromised Websites/Show Items. Subsequently, the app crashes immediately after launching. Removing the app, rebooting the iPad, and downloading a fresh copy of the app from the App Store does not resolve the problem, with the exception that I can launch the app without crashing. Using Compromised Websites again causes a crash.

1Password Version: 8.9.7
Extension Version: Not Provided
OS Version: iPad OS 16.2
Browser:_ 1Password App
Referrer: forum-search:https://1password.community/search?Search=1Password8%20iOS%20app%20crashes%20after%20taping%20Watchtower%2FCompromised%20Websites%2FShow%20Items

Seeing this as well. I removed the app and reinstalled from ten AppStore and it started working again.

Same problem

Hi all.

Yes, this is a known bug with the current version of 1Password for iOS. The fix for it will be included in the next update. Sorry for the inconvenience it's caused.

— Grey

Problem still seems to be there.

Would be nice to have this update pushed already.

Good to know that this issue has been solved, what is taking so long to implement.