<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>1password on Daniel Compton</title>
    <link>https://danielcompton.net/tags/1password/index.xml</link>
    <description>Recent content in 1password on Daniel Compton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 13:00:00 +1200</lastBuildDate><atom:link href="https://danielcompton.net/tags/1password/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fix 1Password 7 crashing when unlocking on macOS 27 Golden Gate</title>
      <link>https://danielcompton.net/snippets/1password-7-crashes-unlocking-macos-27</link>
      <pubDate>Wed, 16 Sep 2026 13:00:00 +1200</pubDate>
      
      <guid>https://danielcompton.net/snippets/1password-7-crashes-unlocking-macos-27</guid>
      <description>&lt;p&gt;After upgrading to macOS 27 Golden Gate, my beloved copy of 1Password 7 started crashing every time I unlocked it. 1Password 7 has long since left active support and is going to &lt;a href=&#34;https://www.reddit.com/r/1Password/comments/1w4k7qg/1password_7_will_no_longer_sync_with_membership/&#34;&gt;stop working with 1Password hosted accounts&lt;/a&gt; in early 2027, but I&amp;rsquo;ve been using it as I still prefer it to 1Password 8.&lt;/p&gt;
&lt;p&gt;I couldn&amp;rsquo;t see an obvious fix, but I gave Codex the crash dump to see if it could do anything. 3.5 minutes later it had figured out a workaround: disabling the Watchtower service. Watchtower is a 1Password feature that checks for vulnerable, weak, reused, or compromised passwords. Helpful, but not critical to using the app.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>After upgrading to macOS 27 Golden Gate, my beloved copy of 1Password 7 started crashing every time I unlocked it. 1Password 7 has long since left active support and is going to <a href="https://www.reddit.com/r/1Password/comments/1w4k7qg/1password_7_will_no_longer_sync_with_membership/">stop working with 1Password hosted accounts</a> in early 2027, but I&rsquo;ve been using it as I still prefer it to 1Password 8.</p>
<p>I couldn&rsquo;t see an obvious fix, but I gave Codex the crash dump to see if it could do anything. 3.5 minutes later it had figured out a workaround: disabling the Watchtower service. Watchtower is a 1Password feature that checks for vulnerable, weak, reused, or compromised passwords. Helpful, but not critical to using the app.</p>
<p>If you&rsquo;re planning ahead, you can disable Watchtower from Settings before you upgrade to macOS 27, but if you&rsquo;ve already upgraded, then you&rsquo;ll need to disable it with the following terminal command:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">defaults write com.agilebits.onepassword7 watchtowerService -bool <span class="nb">false</span>
</span></span></code></pre></div><p>Quit 1Password completely, run the command in Terminal, then reopen it.</p>
<p>The crash report showed that unlocking had succeeded and 1Password was updating Watchtower when it crashed. The relevant calls were <code>domainVulnerabilityForItem:</code>, <code>OPURLTools</code>, and <code>NSURLComponents</code>.</p>
<p>My best guess is that Watchtower encountered a saved URL that 1Password 7 could no longer parse on macOS 27. The resulting exception wasn&rsquo;t handled, so the whole app crashed. Longer term, you are probably still advised to move off of 1Password 7, but this should keep it running for at least this macOS release cycle.</p>
<p>To turn Watchtower back on, delete the override and restart 1Password:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-sh" data-lang="sh"><span class="line"><span class="cl">defaults delete com.agilebits.onepassword7 watchtowerService
</span></span></code></pre></div>]]></content:encoded>
    </item>
    
  </channel>
</rss>
