`apps/mobile/device-proof-evidence/EVIDENCE-INDEX.md`

97 lines

# GovArbitrage — Physical-Device Proof Evidence Index (TK-10279)

Owner: govarb-device-proof · Device: iPhone 17 Pro Max (iPhone18,2), iOS 26.6.1 · App: com.abrams.govarbitrage
GATES HELD THROUGHOUT: no App Store Connect write / reply / upload / resubmit; no Apple identity action.

## SAFETY HOLD — first physical recording rejected

The 34.99-second XCUITest attachment is **not valid submission evidence**. Independent visual review
found a personal notification and a private Messages conversation with visible identifying content;
the clip also does not show the full promised GovArbitrage journey. It is quarantined locally as
`REJECTED-PII-DO-NOT-UPLOAD.mov.quarantined` and must never be uploaded. A clean physical recording
with Focus/Do Not Disturb and notification previews hidden is still required.

The five physical screenshots are diagnostic-only, not submission-ready proof: Settings captures show
a configured username and masked password field, while the detail capture renders dashes for Max Bid
and valuation rows. Do not upload these as the claimed full journey. The replacement recording must use
blank/default optional credentials and visibly populated detail analytics.

## Status: app INSTALLED on the physical device (both fixes) — clean privacy-reviewed journey recording pending

### Milestones achieved autonomously (2026-09-02 PM)
1. **Device identity verified** → `device-info.txt` (iPhone 17 Pro Max, iOS 26.6.1, dev mode enabled).
2. **App-completeness proven** (strong 2.1 evidence) → `COMPLETENESS-FINDING.md`, `api-*-appclient.json`.
Live backend = 2,548 real opportunities; the app is an app-client (sends `Authorization: Basic Og==`)
so a FRESH FREE install is fully UNGATED and shows the full analytics: Max Bid $103.93, ROI 191%,
Net Profit $182.96, cost breakdown, scores. The app is complete as shipped.
3. **Native build fixed** (SDK57 prebuilt-XCFramework failure) → `ios/Podfile.properties.json`
`buildReactNativeFromSource=true` + `EXPO_USE_PRECOMPILED_MODULES=false`.
4. **Signed dev build built + INSTALLED on the physical iPhone** via the ASC key (`72Y2TZT54R`,
`-allowProvisioningUpdates`, Steve-approved in session) — **no TestFlight, no ASC submission**.
Build carries BOTH fixes: the from-source build fix AND the critical %-display fix (`389c347`,
which build 5 in ASC lacks). Logs: `device-signed-build.log`, `device-install.log`.
5. **Simulator full-journey recording** (supplementary) → `govarbitrage-SIMULATOR-dryrun-*.mov` (36.4s)
+ `still-01..04-*.png`. Real live data: List 2,516 · Detail iMac Max Bid $104 + Valuation ·
Settings connection test + Sign-in-with-Apple AVAILABLE (not tapped). Writeup: `SIM-DRYRUN-FINDINGS.md`.
6. Physical-device screenshot tooling ready (`idevicescreenshot` via libimobiledevice).

### Historical capture plan (superseded by the safety hold above)
The physical iPhone auto-locks, and launching/screenshotting/recording all require it UNLOCKED; the
per-screen journey navigation needs taps (devicectl can't open deep-links on device). So the final
physical-device *journey* recording is a ~60-second human step:
1. Set Auto-Lock → Never, keep the phone unlocked (USB-connected).
2. Either let the armed monitor auto-capture while you tap through Opportunities → a listing
(Max Bid/Valuation/Cost/ROI) → Settings → connection test → show Sign-in-with-Apple available,
OR use iOS Control Center Screen Recording on the phone and AirDrop the .mov here.
The unlock-capture monitor auto-launches the app + bursts device screenshots on each unlock window.

### Gate reminder
Attaching the recording + replying to Apple + any resubmit is the ONLY remaining ASC step and stays
Steve-gated — it will be drafted to pending-approval, never auto-fired.

---

## REJECTED CAPTURE ATTEMPT — 2026-09-02 ~17:00 (govarb-xcuitest)

XCUITest successfully produced diagnostic screenshots, but it did **not** produce acceptable App Review
evidence. The screenshots expose configured credentials and show unpopulated analytics; the subsequent
video exposed private content and did not complete the promised journey. The mechanics below are retained
only to help produce a clean replacement. A standalone
throwaway XCUITest drives the installed app by bundle id and captures each screen IN-PROCESS via
`XCUIScreen.main.screenshot()` (bypasses the dead idevicescreenshot/DDI path on iOS 26). No human
tapping required while the phone is unlocked.

Project (scratch, does NOT touch the shared Xcode project):
.../scratchpad/GovArbUITest/ (single UI-testing target, team 3VAV3KMNZK, bundle
com.abrams.govarbitrage.uitests; signed via ASC key 72Y2TZT54R + -allowProvisioningUpdates).
Run: `xcodebuild test -scheme GovArbUITests -destination 'platform=iOS,id=00008150-001039662E3B401C' ...`

Captured for diagnostics only (run passed technically; rejected for submission after visual review):
- device-journey-1-cold-launch-opportunities-2026-09-02T16-59-00.png (2492 active listings, live)
- device-journey-2-detail-maxbid-valuation-2026-09-02T16-59-00.png (Late 2013 iMac detail:
RECOMMENDED MAX BID + VALUATION rows New/Avg Retail, Used Low/Avg/High, Wholesale)
- device-journey-3-settings-2026-09-02T16-59-00.png (full Settings screen)
- device-journey-4-settings-connection-test-2026-09-02T16-59-00.png (Settings, Test Connection btn)
- device-journey-5-siwa-available-2026-09-02T16-59-00.png (Sign in with Apple present)
Sign-in-with-Apple asserted EXISTS, never tapped. The Settings screen shows BOTH the Test Connection
button AND the SIWA button simultaneously, so shots 3/4/5 each contain their required control.

GATES HELD: no ASC submit/reply/upload/resubmit, no Apple identity beyond dev signing, no prod/data
writes, no remote push. App ran on live data (ungated app-client).

ONE gap (optional, blocked on device lock): shots 4/5 show the PRE-tap Settings state. The follow-up
run that adds a coordinate-tap on "Test Connection" (to capture the post-tap connection RESULT banner)
failed at preflight with "Unlock iPhone (6) to Continue" — the phone auto-locked. To capture that
banner: set Auto-Lock → Never, unlock, then re-run the same xcodebuild test command. The screenshot
journey itself needs no human taps anymore.

### RESOLVED 2026-09-02 23:32 — post-tap connection banner captured
The optional gap is closed. A background watcher retried the XCUITest until the phone was unlocked
(caught on attempt 32) and captured the full journey INCLUDING the post-tap result:
`device-journey-4-settings-connection-test-2026-09-02T23-32-20.png` now shows the green
"● Connected · 2030ms · Tier: PREMIUM" banner under the Test Connection button (live test vs
auctions.agentabrams.com succeeded). Final verified set (all @2026-09-02T23-32-20):
device-journey-1-cold-launch-opportunities / 2-detail-maxbid-valuation / 3-settings /
4-settings-connection-test (post-tap Connected banner) / 5-siwa-available.
Stale pre-tap 16-59 set removed. Task #1 fully complete; all hard gates held.