You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 507ef23
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: android/snapshot-helper/README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,3 +162,7 @@ The release manifest is a stable provider contract for the current helper protoc
162
162
resolve the APK from `apkUrl`, verify `sha256`, install it with `adb install -r <apk>`, and run
163
163
`instrumentationRunner`. Manifests up to 0.21.3 also carried an `installArgs` array; it only ever
164
164
spelled `install -r` (plus `-t` while the helper was `testOnly`), so consumers can ignore it.
165
+
166
+
Capture metadata reports `cacheInvalidated` when the capture cleared the platform node cache through `UiAutomation.clearCache()`. A complete capture with that evidence need not change routes after a control press. Incomplete captures and captures without that evidence retain freshness recovery.
167
+
168
+
Warm application open commands use the same automation session. Close retains the existing foreground and process-absence checks. A failed application command is never resent.
Copy file name to clipboardExpand all lines: android/snapshot-helper/src/main/java/com/callstack/agentdevice/snapshothelper/AccessibilityTreeCapture.java
+11-7Lines changed: 11 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -36,13 +36,13 @@ static void prepare(UiAutomation automation, long quietMs, long timeoutMs)
Copy file name to clipboardExpand all lines: android/snapshot-helper/src/main/java/com/callstack/agentdevice/snapshothelper/AutomationCommandHandler.java
Copy file name to clipboardExpand all lines: android/snapshot-helper/src/main/java/com/callstack/agentdevice/snapshothelper/SnapshotInstrumentation.java
Copy file name to clipboardExpand all lines: docs/adr/0011-interaction-guarantee-contract.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@ Completed process history is in git history.
17
17
- The Apple runner does not resend a mutating command whose first send may have run.
18
18
- Multiple mutating selector matches collapse only if they form one ancestor–descendant chain and every member resolves to the same actionable node. Otherwise, the mutation fails with `AMBIGUOUS_MATCH`. Maestro's explicit expected-point/non-hittable compatibility path stays separate.
19
19
- Keep synthesized iOS gesture policy outside the element dispatch-path matrix.
20
+
- On Android, the press/click moving-target guard samples fresh geometry until the target remains on one surface at one position for 100 ms, within a 1,500 ms transition window. A target that cannot establish that evidence is refused. Other platforms retain their existing guard schedule.
Copy file name to clipboardExpand all lines: docs/adr/0014-session-ref-frame-lifetime.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -194,6 +194,8 @@ A ref-targeting mutation is admitted only when all of these conditions hold:
194
194
195
195
The target is resolved against the authorized frame, never against a newer operational observation by positional coincidence.
196
196
Android freshness captures may verify current identity or provide comparison evidence.
197
+
On Android, an identifier that names exactly one same-local-identity node in both the authorized frame and the observation can carry fresh geometry across a positional reindex when both nodes name the same application package.
198
+
This does not change the frame namespace or authorize a different identity.
197
199
But they must not redefine which node an already-admitted `@eN` authorizes.
198
200
199
201
Read-only ref consumers remain fail-open with a structured staleness warning only when the retained frame contains the evidence necessary to resolve that ref.
0 commit comments