Observed
stim android --remote eas --eas-profile development from a Windows host against trailhead (EAS Android build 9c84e29f, 449 MB debug APK) booted an EAS Android session in 3m17s and then failed at install with STIM_INSTALL_FAILED: UNAUTHORIZED: Lease is not active after 5m44s. agent-device diagnostics from the stim run and from a by-hand repro show the same sequence: lease_allocate with a 60 s TTL, a 1m47s APK upload with no heartbeat during the upload, then the install call against an expired lease.
This is an agent-device large-artifact issue, not stim or Windows: the iOS path (a 30 MB simulator .app) never hits it. Nothing upstream matches yet.
Done when
- An upstream issue is filed against agent-device (lease TTL vs upload duration, or a heartbeat during upload) and linked here.
- Stim, until that lands, either warns before install when the artifact is large relative to a 60 s lease (with the size and the expected upload time) or retries the install once with a fresh lease when agent-device answers
Lease is not active. Whichever is smaller; a silent retry loop is not acceptable.
stim android --remote eas completes install and launch from a Windows host with the trailhead debug build. Note the debug APK is 449 MB; a release-variant EAS profile would be far smaller and worth documenting as the recommended remote Android profile.
Related: the Android --remote path still spawns an adb logcat collector for the session id (commands/android/launch.ts:694), the Android analog of #917 item 2.
Origin: #923 field run. EAS cost of that run: one Android build (27m45s) and one session (~10.5 min).
Observed
stim android --remote eas --eas-profile developmentfrom a Windows host against trailhead (EAS Android build 9c84e29f, 449 MB debug APK) booted an EAS Android session in 3m17s and then failed at install withSTIM_INSTALL_FAILED: UNAUTHORIZED: Lease is not activeafter 5m44s. agent-device diagnostics from the stim run and from a by-hand repro show the same sequence:lease_allocatewith a 60 s TTL, a 1m47s APK upload with no heartbeat during the upload, then the install call against an expired lease.This is an agent-device large-artifact issue, not stim or Windows: the iOS path (a 30 MB simulator .app) never hits it. Nothing upstream matches yet.
Done when
Lease is not active. Whichever is smaller; a silent retry loop is not acceptable.stim android --remote eascompletes install and launch from a Windows host with the trailhead debug build. Note the debug APK is 449 MB; a release-variant EAS profile would be far smaller and worth documenting as the recommended remote Android profile.Related: the Android
--remotepath still spawns anadb logcatcollector for the session id (commands/android/launch.ts:694), the Android analog of #917 item 2.Origin: #923 field run. EAS cost of that run: one Android build (27m45s) and one session (~10.5 min).