mirror of
https://github.com/software-mansion/argent.git
synced 2026-09-14 19:27:14 +08:00
Filip131311
b3319b33e0
view-network-logs installs the fetch() interceptor the first time it runs, so traffic the app issued before that is never recorded. The empty result said 'Network interception is active', which reads as a verdict — the app made no requests — when it actually described a state the call had just created. The interceptor now stamps when it started and the read script returns the elapsed window, computed app-side so no host/device clock comparison is involved. The empty result quotes that number instead of picking a threshold: 'recording for 2 ms' reads as 'you have learned nothing yet', 'recording for 14 min' reads as a real empty result, and the same sentence covers both. Three things the log could not previously distinguish are now separate: a window that just opened, a window of unknown length (an interceptor left by an earlier session has no timestamp — defaulting that to 'now' would report 0 ms forever), and nothing recording at all. That last case is why the check moved to the count read: injection is swallowed as non-fatal in two places, so a runtime where it failed was reporting 'interception is active'. Also names the two silent exclusions that make an empty log ambiguous — only fetch() is patched, so an XHR-based client such as axios shows nothing, and Metro's own traffic is filtered out — and replaces the suggestion to reconnect with 'network-inspector-connect', a tool that does not exist.