Expo Go client and Metro bundler: Propagation of developer‑defined fetch timeouts

Expo’s managed workflow wraps fetch/XMLHttpRequest calls and forwards AbortController signals to the native HTTP stack, but the documentation does not state whether a developer‑specified timeout value (e.g., fetch(url, { timeout: 5000 }) or a timeout polyfill) is honored when the request runs through Expo Go.

The underlying native stack may apply its own default (≈30 s) or the OTA update mechanism’s hard‑coded timeout, creating uncertainty about the actual limit enforced and whether timeout‑related errors can be distinguished from explicit aborts.

Does Expo’s managed workflow respect custom timeout values set on fetch requests? If they are ignored, what timeout is actually applied? Is there a way to configure or override the internal timeout used by Expo’s networking layer?