<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle">
  <channel>
    <title>Tscribe</title>
    <link>https://updates.docmayscience.com/appcast.xml</link>
    <description>Updates for Tscribe (Standard edition)</description>
    <language>en</language>
    <item>
      <title>Version 2.1.2</title>
      <pubDate>Mon, 13 Jul 2026 22:30:34 +0000</pubDate>
      <sparkle:version>19</sparkle:version>
      <sparkle:shortVersionString>2.1.2</sparkle:shortVersionString>
      <sparkle:minimumSystemVersion>14.0</sparkle:minimumSystemVersion>
      <description><![CDATA[
<p><strong>Critical.</strong> Fixes a bug that could leave Tscribe impossible to quit or update.</p>
<h4>Fixed</h4>
<ul>
<li><strong>The first-run update question could freeze the app.</strong> It was shown as a modal sheet, and answering it didn&#x27;t take it down — so the question stayed on screen forever. macOS refuses to quit an app while a modal sheet is up, so ⌘Q, the close button, and the updater&#x27;s &quot;Install and Relaunch&quot; all silently did nothing. Force quit was the only way out, and the update could never install. Anyone seeing that question on a fresh install of 2.1.0 or 2.1.1 could hit it.</li>
</ul>
<p>The question is now a normal full-window screen, like the first-launch setup screen. It has no modality, so it cannot block anything: you can quit at any time, answered or not, and the update installs as it should. If you quit without answering, you&#x27;ll simply be asked again next launch.</p>
<p>If you are on 2.1.0 or 2.1.1 and Tscribe seems stuck on the update question, force quit it (⌥⌘Esc), reopen, and answer the question — then update to 2.1.2, which cannot do this.</p>
      ]]></description>
      <enclosure url="https://github.com/jwmay/tscribe/releases/download/v2.1.2/Tscribe.zip" type="application/octet-stream" sparkle:edSignature="se21wPnt0gNLm2yLTDAzATMkmYW3wtR2EpnhIuxCDKHy1gTocDuq+8VD2iL8M6tuJM8N386Z/gYsldL2aPmOCg==" length="43578993" />
    </item>
  </channel>
</rss>
