zscaler-ios-simulator-supabase

Diagnose and fix Supabase network failures in iOS Simulator behind Zscaler managed proxies.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/shoshoavi/agentic_worflows --skill zscaler-ios-simulator-supabase-shoshoavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zscaler-ios-simulator-supabase
Source: https://github.com/shoshoavi/agentic_worflows/tree/main/cursor/skills/zscaler-ios-simulator-supabase
Command: npx skills add https://github.com/shoshoavi/agentic_worflows --skill zscaler-ios-simulator-supabase-shoshoavi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Expo Go or React Native apps work on a real device but fail in the iOS Simulator on a managed Mac with Zscaler or forced PAC proxy settings, with Supabase auth requests like /auth/v1/token failing with Network request failed before any response. ## Core Features & Use Cases - Root Cause Diagnosis: Distinguishes simulator-only transport failures from app-code bugs by comparing real-device behavior and inspecting macOS proxy state with scutil --proxy. - Certificate Trust Workflow: Exports the Zscaler root CA from the macOS System keychain and installs it into the booted iOS Simulator keychain using xcrun simctl. - Verification and Escalation: Validates reachability via Safari in the simulator against /auth/v1/settings and guides escalation to IT for *.supabase.co SSL-inspection bypass. - Use Case: Your Expo app logs in fine on your iPhone but every Supabase auth call fails in the simulator on your corporate Mac, and the proxy toggle keeps re-enabling itself. Follow the workflow to trust the corporate root CA in the simulator and restore connectivity. ## Quick Start Ask the assistant to diagnose why Supabase auth fails with Network request failed in the iOS Simulator while the same Expo app works on a real device behind Zscaler.

Frequently Asked Questions about zscaler-ios-simulator-supabase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does Supabase auth fail in iOS Simulator but work on a real device?▼

The iOS Simulator uses the Mac's managed network path, so Zscaler or forced PAC proxy SSL inspection intercepts its traffic while the real phone bypasses it. The failure is transport-level TLS interception, not an app-code or credentials problem.

How do I fix Network request failed on /auth/v1/token in Expo Go?▼

Export the Zscaler root CA from the macOS System keychain with security find-certificate, then trust it in the booted simulator using xcrun simctl keychain booted add-root-cert. Restart the simulator and Expo, then re-test the auth request.

Does NODE_TLS_REJECT_UNAUTHORIZED=0 fix Expo Go network errors?▼

No. NODE_TLS_REJECT_UNAUTHORIZED=0 only affects Node.js processes running on the Mac. It does not change TLS behavior for Expo Go or native iOS traffic inside the simulator.

How can I verify Supabase is reachable from the iOS Simulator?▼

Open Safari inside the simulator and navigate to your project's /auth/v1/settings URL. A JSON response such as No API key found confirms the endpoint is reachable through the network path.

What if trusting the Zscaler certificate does not fix the simulator?▼

Escalate to your IT or security team and request a no-inspect or bypass rule for *.supabase.co. Until then, use a real device for day-to-day development since it bypasses the managed proxy path.