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
`Interactive snapshot is empty after filtering ${analysis.rawNodeCount} raw Android nodes. Likely causes: the app content is not accessibility-visible yet, a transient route change, or depth/filter options hid the target.`,
231
-
);
232
-
if(
233
-
typeofparams.options.depth==='number'&&
234
-
typeofanalysis.maxDepth==='number'&&
235
-
analysis.maxDepth>=params.options.depth+2
236
-
){
237
-
warnings.push(
238
-
`Interactive output is empty at depth ${params.options.depth}; retry without -d.`,
`Interactive snapshot is empty after filtering ${analysis.rawNodeCount} raw Android nodes. Likely causes: the app content is not accessibility-visible yet, a transient route change, or depth/filter options hid the target.`,
251
+
];
252
+
if(
253
+
typeofparams.options.depth==='number'&&
254
+
typeofanalysis.maxDepth==='number'&&
255
+
analysis.maxDepth>=params.options.depth+2
256
+
){
247
257
warnings.push(
248
-
`Android snapshot helper unavailable; using stock UIAutomator dump, which can time out on busy React Native UIs.${reason}`,
258
+
`Interactive output is empty at depth ${params.options.depth}; retry without -d.`,
249
259
);
250
260
}
261
+
returnwarnings;
262
+
}
251
263
252
-
if(hasReactNativeOverlay(params.snapshot.nodes)){
253
-
warnings.push(
254
-
'Possible React Native warning/error overlay detected. Capture screenshot --overlay-refs, check react-devtools errors if connected, dismiss Dismiss/Close only if unrelated, re-snapshot, and report it.',
'Recent snapshots dropped sharply in node count, which suggests stale or mid-transition UI. Use screenshot as visual truth, wait briefly, then re-snapshot once.',
`Recent ${freshness.action} was followed by a nearly identical snapshot after ${freshness.retryCount} automatic retr${freshness.retryCount===1 ? 'y' : 'ies'}. If you expected navigation or submit, the tree may still be stale. Use screenshot as visual truth, wait briefly, then re-snapshot once.`,
281
-
);
282
-
}elseif(freshness.reason==='sharp-drop'){
283
-
warnings.push(
284
-
'Recent snapshots dropped sharply in node count, which suggests stale or mid-transition UI. Use screenshot as visual truth, wait briefly, then re-snapshot once.',
285
-
);
286
-
}
287
-
}
297
+
constSTALE_SNAPSHOT_DROP_WARNING=
298
+
'Recent snapshots dropped sharply in node count, which suggests stale or mid-transition UI. Use screenshot as visual truth, wait briefly, then re-snapshot once.';
`Recent ${freshness.action} was followed by a nearly identical snapshot after ${freshness.retryCount} automatic retr${freshness.retryCount===1 ? 'y' : 'ies'}. If you expected navigation or submit, the tree may still be stale. Use screenshot as visual truth, wait briefly, then re-snapshot once.`,
)} to expand or clear it; if Dismiss/Close appears, press it, then snapshot -i and report the warning/error in the final summary.`;
331
+
}
332
+
return'Possible React Native warning/error overlay detected. Dismiss visible Dismiss/Close before continuing, then snapshot -i and report the warning/error in the final summary. Use screenshot --overlay-refs only if visual evidence is required.';
)}, then snapshot -i and report the error in the final summary. Prefer Minimize over Dismiss when the error may re-render immediately.`;
371
+
}
372
+
return'Possible React Native warning/error overlay detected. React Native RedBox stack overlay detected. Do not press Dismiss if the error may re-render immediately; use screenshot --overlay-refs if visual evidence is required and report the error in the final summary.';
0 commit comments