<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>IOS on Phosphor BBS</title>
		<link>https://phosphorbbs.net/tags/ios/</link>
		<description>Recent content in IOS on Phosphor BBS</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://phosphorbbs.net/tags/ios/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Five Bugs in One Morning: Debugging the Phosphor iOS Client</title>
				<link>https://phosphorbbs.net/blog/five-bugs-in-one-morning-debugging-the-phosphor-ios-client/</link>
				<pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/five-bugs-in-one-morning-debugging-the-phosphor-ios-client/</guid>
				<description>&lt;p&gt;The &lt;a href=&#34;https://phosphorbbs.net/blog/a-qr-code-on-a-text-screen-pairing-phones-to-a-bbs-without-a-login&#34;&gt;QR pairing post&lt;/a&gt; ended with a working native iOS client for Phosphor BBS. What it didn&amp;rsquo;t cover is what happened next: the app crashed randomly, the keyboard never appeared, and the whole UI rendered in a sad little window in the middle third of the screen. One morning of debugging later, every bug had a root cause, and every root cause was a lesson worth writing down.&lt;/p&gt;&#xA;&lt;p&gt;This is a war story. Five bugs, five root causes, and the one thread that ties them together: &lt;strong&gt;things that pass every test and still fail on real hardware.&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
