Add iOS dev builds documentation #218
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/testflight-and-direct-install"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
docs/ios-dev-builds.mdcovering TestFlight, wireless Xcode, and USB install methodsCloses #108
Changes
docs/ios-dev-builds.md: new doc -- three install methods, comparison table, Fastlane lanes, troubleshootingREADME.md: added iOS Dev Builds row to documentation tableTest Plan
Review Checklist
Related Notes
ldraney/landscaping-assistant #108-- Turbo Native iOS projectlandscaping-assistant-- project this work belongs toPR #218 Review
DOMAIN REVIEW
Tech stack: Documentation only (Markdown). No application code changes. The PR adds
docs/ios-dev-builds.md(155 lines) covering TestFlight, wireless Xcode installs, and USB installs, and adds the doc to the README documentation table.Content quality: The doc is well-structured -- three install methods with clear prerequisites, step-by-step instructions, a comparison table, Fastlane lane definitions, and a troubleshooting section. The "When you need a new build" section is a valuable addition that will save repeated questions about web-only vs native rebuilds.
Accuracy concern: The Fastfile example shows
increment_build_numberwithout specifying axcodeprojparameter. If the iOS project has a non-standard name or path, this may fail silently or increment the wrong target. Minor since this is documentation, not executable code in this repo.BLOCKERS
CLAUDE.md symlink missing from diff: The PR title, summary, and changes section all claim a
CLAUDE.mdsymlink toREADME.mdwas added, but the diff contains only 2 changed files (README.mdanddocs/ios-dev-builds.md). The symlink is either not committed or was dropped before push. The PR description does not match the actual content.This is a BLOCKER because it represents a gap between stated deliverables and actual changes. Either:
NITS
README table ordering: The new row is inserted between Multi-Database and a missing
Local Dev Setupentry. On the current main branch, the row after Multi-Database isTesting Strategy. The diff showsLocal Dev Setupbelow the new row, but that entry does not exist on main today. This suggests the PR branch may be based on a stale or different state of main, or there are uncommitted/missing changes. Worth verifying the branch is rebased on current main.Apple Team ID in docs:
HAY64YD5PXis included in the doc. While Team IDs are semi-public (visible in App Store metadata), consider whether this belongs in a repo that may become more widely shared. Not a blocker for a private repo.SSH command style:
ssh macbook "cd ~/landscaping-assistant-ios && fastlane beta"assumes a hostname aliasmacbook. Consider adding a note that this requires SSH config or substituting the actual host.SOP COMPLIANCE
PROCESS OBSERVATIONS
VERDICT: NOT APPROVED
Single blocker: the CLAUDE.md symlink is described in the PR but absent from the diff. Fix the discrepancy (either add the symlink or update the PR description), then re-request review.
Add iOS dev builds doc and CLAUDE.md symlinkto Add iOS dev builds documentationPR #218 Review
DOMAIN REVIEW
Tech stack: Documentation only (Markdown). 2 files changed, +156 lines, 0 deletions.
Scope: New
docs/ios-dev-builds.mdcovering three iPhone install methods (TestFlight, wireless Xcode, USB) plus Fastlane setup and troubleshooting. README updated to add the doc to the documentation table.Content quality: The doc is well-structured with clear section hierarchy, a useful comparison table, actionable commands, and a practical troubleshooting section. The "When you need a new build" section is particularly valuable -- it clarifies the web-only vs native-rebuild boundary, which is the most common question for turbo-ios projects.
Cross-reference consistency issue: The existing
docs/pipeline.mduses~/landscaping-iosas the local project path (lines 95, 113, 122), while this new doc uses~/landscaping-assistant-iosthroughout. One of these is wrong. Recommend aligning to whichever path is actually in use on the MacBook. This is a nit since the doc is instructional and the reader will adapt, but inconsistency across docs creates confusion.Overlap with pipeline.md: Sections 3 and 4 of
docs/pipeline.mdalready cover iOS dev builds and TestFlight/App Store. The new doc duplicates and expands on this content. This is acceptable --pipeline.mdgives the overview whileios-dev-builds.mdis the hands-on reference -- but neither doc cross-references the other. Adding a "See also" line in each would prevent them from diverging silently.BLOCKERS
None. This is a docs-only PR with no code changes, no secrets, and no security surface.
NITS
Path inconsistency:
~/landscaping-assistant-ios(this doc) vs~/landscaping-ios(pipeline.md). Pick one and update both docs.Missing cross-references:
ios-dev-builds.mddoes not link todocs/pipeline.md(which covers the same iOS flows at a higher level).pipeline.mddoes not link to this new doc. A## Relatedsection in the new doc and a line in pipeline.md would help.Apple Team ID in plain text:
HAY64YD5PXon line 8 of the new doc. This is semi-public (visible in provisioning profiles and App Store metadata), so it is not a secret, but consider whether you want it in a public-facing doc. If the repo is private, this is a non-issue.README table ordering: The iOS Dev Builds row is inserted between Multi-Database and Local Dev Setup. Alphabetical or thematic grouping would place it closer to Pipeline and Infrastructure. Minor -- the PR branch appears to already include the expanded table from PR #221, so ordering may have been intentional.
SOP COMPLIANCE
PROCESS OBSERVATIONS
Docs-only PRs are low-risk for change failure. The duplication overlap with
pipeline.mdis worth tracking -- if either doc is updated in the future, the other should be checked for consistency. The path inconsistency (landscaping-iosvslandscaping-assistant-ios) should be resolved before merge to avoid confusing future readers (or agents).VERDICT: APPROVED