Problem
Expo projects that build development clients on EAS cannot explicitly select those builds for a Stim session. On a cache miss Stim compiles locally, requiring the local native build toolchain and bypassing EAS build profiles.
Evidence
Requested while developing Stim. Current origin/main has no EAS profile selector or build download flow. Existing Expo build-cache providers perform cache lookup; --remote eas selects a remote device while builds remain local.
EAS CLI supports build listing by fingerprint and profile, and artifact download by build ID: https://docs.expo.dev/eas/cli/.
Cause
The iOS and Android command pipelines resolve local/provider artifacts and otherwise invoke Xcode or Gradle. They do not explicitly select EAS Build artifacts.
Fix idea
Select compatible completed EAS development builds for iOS simulators, Android emulators, and connected physical devices, download and reuse them locally, and preserve Stim installation, Metro, launch evidence, and device ownership. On a miss, stop with an actionable EAS build command. For an iOS device missing from the artifact's provisioning profile, point to EAS device registration and rebuilding commands. Do not register devices, trigger billable builds, or silently compile locally. Test cache hits, misses, mismatches, lookup failures, and the real EAS CLI invocation.
Problem
Expo projects that build development clients on EAS cannot explicitly select those builds for a Stim session. On a cache miss Stim compiles locally, requiring the local native build toolchain and bypassing EAS build profiles.
Evidence
Requested while developing Stim. Current origin/main has no EAS profile selector or build download flow. Existing Expo build-cache providers perform cache lookup;
--remote easselects a remote device while builds remain local.EAS CLI supports build listing by fingerprint and profile, and artifact download by build ID: https://docs.expo.dev/eas/cli/.
Cause
The iOS and Android command pipelines resolve local/provider artifacts and otherwise invoke Xcode or Gradle. They do not explicitly select EAS Build artifacts.
Fix idea
Select compatible completed EAS development builds for iOS simulators, Android emulators, and connected physical devices, download and reuse them locally, and preserve Stim installation, Metro, launch evidence, and device ownership. On a miss, stop with an actionable EAS build command. For an iOS device missing from the artifact's provisioning profile, point to EAS device registration and rebuilding commands. Do not register devices, trigger billable builds, or silently compile locally. Test cache hits, misses, mismatches, lookup failures, and the real EAS CLI invocation.