TheChosenVictorYour privacy, your choice. Choose whether TheChosenVictor.com may use optional Google Ads measurement or keep advertising storage limited. This website setting does not change the privacy practices of any app.
Website privacy detailsNewsletter / Archive
The published issues, newest first. Expect methods, teardowns, tools, decisions, experiments, and honest product demonstrations.
Open any issue to read it on the site.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
When a recurring publication falls behind, record the missed dates, restore today's complete delivery chain, and verify every public and subscriber surface without inventing a streak.
Approval, App Store Connect distribution, and public storefront availability are three different checks. A release closes only when the intended version clears all three for the storefront being verified.
Four App Store feedback collections were empty across twelve apps. A source-to-build comparison still found eleven uploaded builds older than meaningful fixes.
A Search Console view configured for three months showed visible data from July 12 through August 7: zero clicks across 300 impressions. A page filter and four live checks separated low visibility from a broken destination.
Two apps ship a test whose only job is to fail if the Google ad SDKs come back. Both passed while both lockfiles still pinned the packages. One was reading the right file with markers that could never match it.
Four files went to zero bytes this morning and the shell printed only command not found. In zsh a redirect opens its target before the command is resolved, so a command that never runs still empties the file.
I measured the tree before writing the script that copies it. 231G total, and 201G of that was one folder of old video and game archives that never changes. Excluding it took the routine run down to 26,424 MB and under five minutes.
An open XcodeBuildMCP issue printed the command that reproduces it. On a newer Xcode that command succeeds, because the toolchain started resolving the package the report said it could not resolve. The defect was untouched. A different entry point returned the filed error word for word.
A cache-busted App Store lookup returned 1.0.1 for an app whose 1.0.2 was approved and waiting. A known-live control proved the request worked. It did not prove the request pointed at the right app, and the version it returned was a fact, not a verdict.
I posted a traffic result about an iOS launch kit into a developer subreddit. The top comment said it was marketing, not development, and it outscored the post. Who a product is for does not decide where a post about it belongs.
On July 14 I wrote down the number that would decide whether my $29 kit had failed: 250 qualified product views in two weeks. The window closed on July 28 with 4. So I recorded it as a distribution failure, because the offer never got in front of enough people to pass or fail on its own merits.
A note I wrote on July 12 said SwiftData's rollback() does not revert attribute edits. Sixteen days later I carried it into Kitwise, wrote a test to prove the same bug was there, and the test passed instead. The note had never been checked against that codebase.
A maintainer requested three changes on my open-source pull request. I pushed all three the next morning and never replied on the review threads, so it sat for eight days looking stalled. One point-by-point comment cleared it in under seven hours.
Issue #034 was live on my site, but its email never went out. I tied subscriber delivery to the same deployment and record each completed issue in Postgres so a retry does not put the same message in the inbox twice.
I added one search page for 95 public entries across six site sections. The catalog comes from existing public registries, and React filters it without putting the query in a URL, storage, analytics, server logs, or a backend.
A Sortes gallery image showed a UnitFlip back indicator. Other app pages carried stale screenshots or claims for features that were not shipped, so I audited all twelve pages against current app truth.
Two finished YouTube masters passed every automated check but still needed eight human listening verdicts. Four days later I archived the production system instead of keeping it active because the videos were finished.
I created a receipt with no return or warranty deadline. ReceiptCrate marked it Expired and put it in Alerts anyway. The tests were green because none of them had ever made that exact receipt.
I tried to publish the same book as a paperback and a Kindle eBook. The paperback is live. The eBook is stuck in Draft behind an error banner that highlights nothing, and the publish request comes back with an empty errors object.
Apple's screenshot spec page changed which 6.9-inch resolution it led with between two visits six days apart. The accepted-size list still included all three, which is why I stopped treating one prominent number as the whole spec.
I put AdMob in some of my apps for a little passive revenue. The pennies never covered what the SDK cost me in launch time and a clean privacy label, so I'm pulling it back out one app at a time.
I shipped the same book copy to Amazon's US and UK stores. The US store published it. The UK store flagged one word as violence and blocked the page, and the fix changed how I clear an automated filter now.
I kept changing App Store metadata one field at a time and made the results harder to read. Now I batch the title, subtitle, keywords, screenshots, and preflight checks before I submit.
I finished Product Hunt prep for the kit, checked the real surfaces, and cut the extra outreach. Launch day should be for replies, not panic.
I automated almost a whole publishing workflow today, then hit a wall a browser bot can't cross. The real skill is knowing where to stop and just do the last step by hand.
I sat down to plan the day and half the list was already done. The boring failure nobody warns you about: your records drift from reality.
A build log: two apps went live while my own site hid them, the lesson that came out of it, and a new code-only video style for the channel.
Introducing TheChosenVictor, the vault, and what to expect from this newsletter.
Future issues
Subscribe for new issues and access to the subscriber vault.
Get new issues when they are published.
By subscribing, you agree to our Privacy Policy.