also looking at this
iOS Phase 8: the presented pickers — ratchet 58 → 53, last mechanism landed
#90
11 files
+5752
-12
| @@ -90,7 +90,7 @@ LAUNCH_PID=$! | ||
| 90 | 90 | # The round trip is fast, but a cold simulator is not. Poll rather than sleep a |
| 91 | 91 | # fixed amount, so a slow boot does not read as a failure. |
| 92 | 92 | for _ in $(seq 1 60); do |
| 93 | if grep -q 'i=12' "$LOG" 2>/dev/null && grep -q 'i=14' "$LOG" 2>/dev/null; then sleep 1; break; fi | |
| 93 | if grep -q 'i=18' "$LOG" 2>/dev/null && grep -q 'i=14' "$LOG" 2>/dev/null; then sleep 1; break; fi | |
| 94 | 94 | sleep 1 |
| 95 | 95 | done |
| 96 | 96 | kill "$LAUNCH_PID" 2>/dev/null || true |
| @@ -172,4 +172,13 @@ C60="$(count 60)" | ||
| 172 | 172 | [ "$C60" -ge 1 ] || { echo "FAIL: startMotionUpdates never reached the dispatcher"; exit 1; } |
| 173 | 173 | echo "ok: event-driven action dispatched to Zig (i=60 seen ${C60}x)" |
| 174 | 174 | |
| 175 | C18="$(count 18)" | |
| 176 | # The fixture has no NSCameraUsageDescription, and presenting a camera picker | |
| 177 | # without one TERMINATES the process — so the module refuses before it ever | |
| 178 | # asks whether hardware exists, with PERMISSION_DENIED. What is asserted | |
| 179 | # is that the code is specific: the generic NATIVE_CALL_FAILED would send | |
| 180 | # whoever reads it looking for a bug that is not there. | |
| 181 | [ "$C18" -ge 1 ] || { echo "FAIL: the refusal did not name its own cause"; exit 1; } | |
| 182 | echo "ok: unavailable hardware refused with a specific code (i=18 seen ${C18}x)" | |
| 183 | ||
| 175 | 184 | echo "PASS" |