<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Chase Martin</title>
    <link>https://chasemartin.dev/</link>
    <description>Notes on shipping iOS apps end to end.</description>
    <language>en</language>
    <atom:link href="https://chasemartin.dev/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Every form crashed when the keyboard appeared</title>
      <link>https://chasemartin.dev/blog/swift-6-isolation-crash-swiftui-keyboard/</link>
      <guid isPermaLink="true">https://chasemartin.dev/blog/swift-6-isolation-crash-swiftui-keyboard/</guid>
      <description>A Swift 6 isolation check killed the app on iOS 27 the moment a software keyboard came up. The closure that trapped was never marked @MainActor. It inherited the isolation, and SwiftUI handed it to a renderer that does not run there.</description>
      <pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Building shared infrastructure across independent iOS products</title>
      <link>https://chasemartin.dev/blog/shared-infrastructure-across-ios-products/</link>
      <guid isPermaLink="true">https://chasemartin.dev/blog/shared-infrastructure-across-ios-products/</guid>
      <description>I maintain shared infrastructure across independent iOS products, with one currently live on the App Store. This post explains how I keep that foundation coherent, what it costs, and where product-specific behavior deliberately stays separate.</description>
      <pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
