feat(ios): refresh onboarding setup flow#98868
Conversation
|
Codex review: needs maintainer review before merge. Reviewed July 5, 2026, 6:44 PM ET / 22:44 UTC. Summary PR surface: Tests +18, Other +1008. Total +1026 across 16 files. Reproducibility: not applicable. this is a user-facing iOS UX refresh rather than a bug report. The relevant proof path is the simulator walkthrough and UI/smoke coverage for onboarding, setup code, success, and Chat handoff. Review metrics: 1 noteworthy metric.
Stored data model Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Risk before merge
Maintainer options:
Next step before merge
Maintainer decision needed
Security Review detailsBest possible solution: Land the refreshed iOS onboarding/setup flow after the assigned iOS reviewer accepts the UX direction and exact-head CI finishes; if not accepted, narrow the visual refresh instead of adding a parallel setup path. Do we have a high-confidence way to reproduce the issue? Not applicable: this is a user-facing iOS UX refresh rather than a bug report. The relevant proof path is the simulator walkthrough and UI/smoke coverage for onboarding, setup code, success, and Chat handoff. Is this the best way to solve the issue? Yes for implementation shape, pending product acceptance: the code stays in the iOS onboarding/quick setup owner boundary, uses branded typography/i18n coverage, and adds focused UI/render tests. The remaining question is whether maintainers want this exact first-run UX direction. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against 37c67b0d27b3. Label changesLabel changes:
Label justifications:
Evidence reviewedPR surface: Tests +18, Other +1008. Total +1026 across 16 files. View PR surface stats
What I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
Review history (23 earlier review cycles; latest 8 shown)
|
954c11e to
1b4affb
Compare
1b4affb to
ae10b98
Compare
b028622 to
30032d7
Compare
f014fd2 to
25d32a0
Compare
25d32a0 to
55d8610
Compare
50a1fe9 to
7a5cbda
Compare
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
@clawsweeper re-review |
|
@clawsweeper re-review Current head |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
Maintainer finish-line update pushed: What changed in the maintainer refresh:
Local proof run on the pushed diff before force-with-lease:
Simulator proof artifact from the final local run:
Known caveat: Xcode repeatedly rewrote @clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
Maintainer follow-up pushed: This rebases the PR cleanup onto current Local proof on the pushed SHA:
Notes:
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
Follow-up pushed: Addressed the review finding about the completed onboarding CTA: the success screen now restores the explicit destination cue from current main, using Additional local proof on the rebased SHA (
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
@clawsweeper re-review |
…refresh-clean-98868 # Conflicts: # apps/ios/Sources/Onboarding/OnboardingWizardView.swift





What Problem This Solves
The iOS first-run and gateway setup surfaces had uneven visual treatment and unclear setup hierarchy, which made a new user's first impression feel less polished than the rest of OpenClaw.
Summary
Refreshes the onboarding and gateway setup flow with OpenClaw-branded UI polish, clearer QR/manual setup steps, and SwiftUI smoke coverage for the updated screens.
Evidence
d8a67249eb.--openclaw-reset-onboarding --openclaw-initial-tab settings --openclaw-initial-destination settingsand verified: onboarding intro withContinue/Close, Connect Gateway withopenclaw qrandConnect Manually, manual setup withEnter setup code,APPLE-REVIEW-DEMOsetup code application, success state withYou're connected,Apple Review Demo Gateway, andGo to Chat, then Chat tab selected after tappingGo to Chat.OpenClawTests/OnboardingRefreshGuardTests: 3 passed, 0 failed.OpenClawUITests/OpenClawSnapshotUITests/testOnboardingPairCommandAndCompletionOpenChat: 1 passed, 0 failed.pnpm native:i18n:check: passed.swiftformat --lint --config config/swiftformaton touched Swift files: passed.git diff --check: passed.