Archive
The published issues, newest first. Expect methods, teardowns, tools, decisions, experiments, and honest product demonstrations.
Published issues
Showing 12 of 40
The Lookup Price Is Not the Customer Price
A cache-busted US lookup returned Free for UnitFlip, QRift, and VaultSnap, and $6.99 for Sortes. The IAP block is a second public number on the free listings. A candidate version in App Store Connect is a third number, and it is not live.
Your Visitor Count Is 103 Times Too Big
A raw visitor count off a server log is not traffic. Six days of mine said 4,958 pageviews from 529 visitors. Verified: 48, from 21 addresses.
The Fix Shipped and the Bug Is Still Live
My one-line fix for a soft 404 is committed, deployed, and in the compiled output. The running site says the bug is still there. Three of the four places I checked were wrong.
305 Tests Failed and None of Them Was a Bug
My test suite went from green to 305 failures without a line of code changing. The cause was one environment variable set in the shell that started it, and the fix belongs in the config, not the shell.
Your First Duplicate-File Count Is Wrong
Hashing every source file across my apps reported two files shared between projects. Both were Xcode build output, sitting in a directory my exclude list did not match.
The Upload Check and the Running App Read Different Files
A commit said the shipped build had no HealthKit usage description. The built Info.plist agreed. The running app disagreed, and the permission sheet rendered the explanation anyway.
Pixel Size Is Not a Locale Check
496 localized App Store finals already measure 1320x2868. Opening six of them showed five leftover English-chrome notes were stale, and one Hindi mood screen still had an extra invented chip.
409 Green Tests Missed Three Persistent-State Defects
Three full simulator suites passed 409 tests. Persistent-state walkthroughs then found a stuck setup screen, a lost Files exporter, and a recovered drive saved as zero minutes.
Search the Store Before You Publish the Name
A public product URL is a name claim. Search the live US App Store for the exact name, in the same job, before you put that name on support, privacy, or terms pages.
The Report Named the Wrong Route
Two routes were reported as returning 500. Thirty-four live requests and ten days of the server's own access log said they had never returned anything but 200, and the log named the route family that actually failed.
launchctl submit Kept the App Alive
Two leftover launchctl submit jobs reopened a local macOS app after every quit. Apple's man page says submit tells launchd to keep the program alive in the event of failure, so a one-shot repair helper can outlive the repair.
One Row Cannot Prove One Sender
A send guard read its status row and wrote to it in two statements, so two simultaneous requests both passed it. Use this to decide when a clean record is evidence.
Get new issues when they are published.
By subscribing, you agree to our Privacy Policy.