What problem does it solve? React Native apps often work on real devices but fail in iOS Simulator or Android Emulator due to corporate proxies, Zscaler TLS inspection, stale Expo Go state, or flaky emulator images, and this Skill provides a structured triage flow to isolate the environment as the root cause instead of rewriting app code. ## Core Features & Use Cases - Environment-first triage: Separates app-code bugs from simulator, proxy, and TLS issues by comparing real-device behavior against simulator behavior. - Corporate proxy and Zscaler handling: Walks through checking macOS proxy state with scutil and trusting the Zscaler root CA inside the iOS Simulator keychain. - Safe network diagnostics: Shows how to wrap global.fetch around a Supabase client to log method, host, status, and errors without leaking tokens or headers. - Use Case: Your Expo app logs in fine on a physical iPhone but throws "TypeError: Network request failed" on the iOS Simulator behind a corporate Zscaler network; this Skill guides you to trust the root CA in the simulator and request a no-inspect rule for *.supabase.co. ## Quick Start Ask the assistant to debug why your Expo app fails with a network request error on the iOS Simulator while working on a real device.
