◉CLAUDE LABJP
●CC 2.1.327 — Claude Code 2.1.327 (11/18) adds claude mcp add-json, which reads a server's JSON from stdin●MCP.JSON — The same release stops project-scope mcp add and remove from wiping other keys in .mcp.json●SONNET 4.5 — Retires on the Claude API on 11/30, 11 days left. Sweep model IDs in code and saved settings in one pass●GATEWAY — Users report that behind a gateway, 1M-context models compact so late that each reply takes tens of seconds●NEON — Gemini 4 Neon went GA on 11/18. If you run it next to Claude Code, keep each tool's MCP config separate●NEW — Linked Billing 402 or 403? Find Whose Wallet Is Empty First●CC 2.1.327 — Claude Code 2.1.327 (11/18) adds claude mcp add-json, which reads a server's JSON from stdin●MCP.JSON — The same release stops project-scope mcp add and remove from wiping other keys in .mcp.json●SONNET 4.5 — Retires on the Claude API on 11/30, 11 days left. Sweep model IDs in code and saved settings in one pass●GATEWAY — Users report that behind a gateway, 1M-context models compact so late that each reply takes tens of seconds●NEON — Gemini 4 Neon went GA on 11/18. If you run it next to Claude Code, keep each tool's MCP config separate●NEW — Linked Billing 402 or 403? Find Whose Wallet Is Empty First
Articles/Claude Code
⟐ Claude Code/2026-11-19Advanced

My Porting Checklist Was Written in SwiftUI Terms, and It Couldn't Find a Single Purchase Item in My Objective-C Code

I built a small pipeline that hands Claude Code only the checks relevant to the file I'm editing, out of a 113KB list of 33 Android pitfalls. Three scripts, and how a SwiftUI vs Objective-C vocabulary gap let the most important items slip through.

Claude Code289iOS27Objective-CAndroid9PortingSlash Commands

✦ Premium Article

In early November I was in the middle of moving features from the Android version of my wallpaper app over to the iPhone version. Next to me was a document I had been growing since spring: a list of pitfalls I had stepped on during Android device testing and post-release monitoring, written so that the iOS side would not repeat them. It had reached 33 items and 113KB.

That is far too much to hand Claude Code every time I open a file. So I put together a small pipeline that pulls out only the items relevant to the file being edited. When I tried it on the in-app purchase file, though, not a single purchase-related item came back.

The reason was almost embarrassing. The "iOS check" sections of my document were written in the vocabulary of SwiftUI and StoreKit 2, while the actual iPhone app is written in Objective-C. Both the document and the code are mine, and yet they were speaking different languages. I only noticed because the output was empty.

The short version

What I most want to pass on is this: an item your index fails to find is often not irrelevant. It may simply be written in different words.

Here is what I ended up with: three scripts and one command for calling them from Claude Code.

  • A structure check (duplicate numbers, ordering, missing or split sections)
  • An index that keeps only the "iOS check" section of each item
  • A lookup that matches identifiers in the file you are editing against that index, with a vocabulary bridge and a filter for common words

These are the results from running it against my real document and my real source tree. A lower hit count is not automatically better; what matters is whether the purchase items show up for the purchase file.

StageResult
Structure check34 items (33 plus one sub-numbered item), 4 problems
Index, first version (bullet lines only)8 of 34 items came out empty
Index, fixed version (prose and code included)0 empty items, 113,432 bytes down to 42,884 bytes
Lookup on the purchase file (plain matching)4 items, all matched on generic words like view controller references; 0 purchase items
Same, with common words filtered out0 items
Same, with the vocabulary bridge added5 items: purchase-state flicker, duplicate handling, threading
What Claude Code receivesAbout 3.6KB for the purchase file

An item you cannot find may not be irrelevant; it may just be written in different words. That one sentence is the line I drew from this work.

What the document looks like, and which part Claude Code needs

Every item in the pitfalls list has four sections:

  • Symptom: what happened
  • Cause: why it happened, structurally
  • Android fix: how I fixed it
  • iOS check: what to verify on the iOS side so the same thing doesn't happen again

While I'm porting, what Claude Code actually needs is almost always the last one. The symptom and cause are background for my own judgment, and the Android fix is Java, which doesn't transfer to the iPhone code as-is. So I settled on two layers: an index of the check sections, keyed by item number, and the full document for the occasional item where the backstory matters.

The catch is that if the document's shape isn't consistent, items quietly fall out during extraction. I had been adding to this file for months, and its shape had drifted more than I realized.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦You will be able to catch, before a port begins, the case where your checklist and your codebase speak different languages and the most important checks silently never match
✦You can now hand Claude Code only the checks that matter for the file you are editing, instead of making it read a 33-item, 113KB pitfalls document every time
✦You will be able to detect drifting section names and numbering mechanically, before your index quietly drops items
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

⟐ Claude Code2026-10-12
After Moving to SPM, My App Died the Moment It Launched — Reading One dyld Line with Claude Code
Right after moving from CocoaPods to Swift Package Manager, the build passed but the app died on launch. Here is how I traced one dyld line to its cause, the fix, and how to verify it.
⟐ Claude Code2026-09-04
The One File I Keep Out of Claude Code's Reach: project.pbxproj
With Xcode project files, the breakage that still opens costs far more than the breakage that refuses to open. Here is what I measured before moving every edit behind a script, and where the line sits today.
⟐ Claude Code2026-08-12
When Paying Users Still See Ads: Collapsing the Ad-Free Check Into One Place
A user who paid to remove ads still sees them. The cause is rarely a missing flag — it is a check that lives in too many places. Here is how I inventoried every ad call with Claude Code and folded the decision into a single gate.