feat(swift-example-app): debounced live validation of faucet RPC password

[QuantumExplorer]

Issue being fixed or feature implemented

The "Faucet RPC Password" field on OptionsView (regtest + Use Docker Setup branch) silently persisted whatever was typed. Auth failures surfaced only later, when the user tapped "Request from faucet" on `ReceiveAddressView` and got a 401 with no obvious reason.

Compounding factor: dashmate randomizes every Core RPC user's password at `setup local` time (`setupLocalPresetTaskFactory.js`: `options.password = generateRandomString(12)`). The base config template's `rpcpassword` literal never matches a real local cluster, so anyone copy-pasting from the dashmate base config docs hits 401 with no inline signal.

What was done?

`packages/swift-sdk/SwiftExampleApp/SwiftExampleApp/Views/OptionsView.swift`:

• Added a local `@State faucetPassword` seeded from the existing `UserDefaults` key. `.onChange` writes through to the same key on every keystroke so other consumers (`ReceiveAddressView.requestFromFaucet`) keep reading the canonical value with no behavior change.
• Wrapped the field in a `.task(id: faucetPassword)` debouncer: every keystroke changes the id, SwiftUI auto-cancels the prior task (`Task.sleep` throws `CancellationError`), the new one starts. After 500ms of stable input, validation runs.
• Validator issues a single `getblockcount` JSON-RPC against `http://127.0.0.1:/` with HTTP basic auth (`<faucetRPCUser=dashmate>:`) and a 3-second timeout. Status maps cleanly:
  • 200 → ✓ "Authorized" (green)
  • 401 / 403 → ✗ "Wrong password" (red)
  • any other HTTP / network error → ⚠ "Unreachable (...)" (orange) — covers Docker-not-running via connection-refused
  • empty field → status row hidden
• Inline status row below the field: `ProgressView` while checking, otherwise SF Symbol + label colored to match.
• On view appear, `.task(id:)` fires once with the persisted value, so the badge reflects current state without requiring the user to retype.

How Has This Been Tested?

• `xcodebuild -project SwiftExampleApp.xcodeproj -scheme SwiftExampleApp -sdk iphonesimulator` passes.
• Manually on the simulator pointed at a running dashmate local cluster:
  • Empty field → no status row.
  • Type `rpcpassword` (the template default) → after 0.5s, ✗ "Wrong password" (red).
  • Replace with the real password from `yarn dashmate config get --config=local_seed core.rpc.users.dashmate.password` → after 0.5s, ✓ "Authorized" (green).
  • Stop the dashmate cluster → after 0.5s, ⚠ "Unreachable (Could not connect to the server.)" (orange).
  • Rapid typing while validation is in flight cancels the prior request and only the latest stable value gets validated — no thundering-herd of RPCs.

Breaking Changes

None. The `UserDefaults` storage key, format, and write-through behavior are unchanged. The only addition is the inline status indicator and the background probe.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@QuantumExplorer has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 57 minutes and 8 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3e1f29ca-8087-4ccd-abc2-88e14664df10

📥 Commits

Reviewing files that changed from the base of the PR and between 318d83b and c3afb01.

📒 Files selected for processing (1)

• packages/swift-sdk/SwiftExampleApp/SwiftExampleApp/Views/OptionsView.swift

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/swift-example-app-faucet-password-validation

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[thepastaclaw]

Review Gate

Commit: c3afb01d

• ✅ Debounce: 48m ago (need 30m)

• ✅ CI checks: builds passed, 0/2 tests passed

• ✅ CodeRabbit review: comment found

• ⏳ Off-peak hours: peak window (5am-11am PT) — currently 06:16 AM PT Tuesday

• Run review now (check to override)

[QuantumExplorer]

Self Reviewed

[github-actions]

✅ DashSDKFFI.xcframework built for this PR.

• Workflow run: https://github.com/dashpay/platform/actions/runs/25376385790
• Artifacts: DashSDKFFI.xcframework (folder), DashSDKFFI.xcframework.zip, xc_checksum.txt

SwiftPM (host the zip at a stable URL, then use):

.binaryTarget(
name:"DashSDKFFI",
url:"https://your.cdn.example/DashSDKFFI.xcframework.zip",
checksum:"d0a27292127db0d5e64d42da6469bb00ee2304245db7c4d75b3dc73b1538fb76")

Xcode manual integration:

• Download 'DashSDKFFI.xcframework' artifact from the run link above.
• Drag it into your app target (Frameworks, Libraries & Embedded Content) and set Embed & Sign.
• If using the Swift wrapper package, point its binaryTarget to the xcframework location or add the package and place the xcframework at the expected path.