* [eas-cli] make command descriptions lowercase without trailing periods
Most command descriptions in eas --help already start lowercase and end
without a period; align the remaining 11 capitalized and 12 period-terminated
ones with that style. Proper nouns, [EXPERIMENTAL] prefixes, and later
paragraphs of multi-line descriptions are unchanged.
* [eas-cli] Drop trailing periods from simulator command descriptions
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
# Why
I want to set up billing and limits for sandboxes so we need to be able to say how long can a sandbox run for.
# How
Added simple `max_duration_seconds` like we have in agent runs and device run sessions.
# Test Plan
CI should pass.
Look up why a failed simulator session failed in both simulator:start and
simulator:get. For unknown errors, read the failed step's cause from the job
run log, using only the masked log message, with the download bounded by size
and time. Strip terminal control characters before printing.
* [eas-cli] Show why a simulator session failed to start
simulator:start only printed the session status when a session errored
before it was ready. The reason is already on the session's job run, so
fetch turtleJobRun.errors and print each message (and docs link) on its
own line.
* [eas-cli] Read simulator job run errors only on failure, and from logs for unknown errors
Fetch job run errors with a separate query when a session fails instead of
on every poll of the shared session query. When the job run only reports an
unknown error, print the failed step errors from its logs. Also show the
errors when a session fails after it is ready.
* [eas-cli] Show only structured job run errors in simulator:start
Drop the job run log fallback from this change, which printed unmasked
err.message lines, read logs for stopped sessions and had no timeout or size
limit. The bounded, masked log fallback lands in the simulator:get follow-up.
* [eas-cli] Bound and quiet the simulator job run errors lookup
Give the lookup a 10s deadline and the session's Ctrl+C signal, and cancel
its request by unsubscribing from urql, so it can't hold up stopping the
session. Don't retry it or print the transient-error message, since it's
best-effort. Cap each error message at 500 characters.
* [worker] Mask secrets in logged errors
The upload transform masked only each record's msg, so a serialized err
(message, stack and other fields) was uploaded with secrets intact. That
includes unknown build phase failures, which log { err } with an empty msg.
Mask the strings inside err on a copy, since bunyan shares the record with
other streams.
* [worker] Mask secrets in every field of uploaded log records
Mask all fields except bunyan's metadata, not only err: other fields such as
error, data and the job dump also carried secrets. Round-trip each value
through JSON first so a toJSON method can't bring back the original, mask keys
and numbers, and replace values nested too deeply instead of uploading them
unmasked.
* [build-tools] Check Android launch inputs before the emulator boots
Agent-device sessions checked Android launch inputs only when launching,
after the emulator booted and the build installed. Check NUL characters
and the command length at the start of the step, as on iOS, leaving room
for the launch component that is only known after install.
* Add changeset for early Android launch input checks
* [eas-build-job] Share the Android launch input checks
Move the Android shell quoting and the early launch input checks into
@expo/eas-build-job, so www can check launch inputs when a session is
created, for every session type.
* [eas-build-job] Check only the known part of the Android launch command early
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
* [build-tools] Quote Android launch arguments for the device shell
adb shell joins its arguments with spaces and the device shell parses the
result again, so a launch argument such as "hello world" reached am start
as two words and the launch failed. Quote each word, reject commands that
adb cannot carry, and reject empty arguments that are not extra values.
* [build-tools] Pass empty Android launch arguments through and reject NUL
Guessing which am start option an empty argument belongs to rejected
valid input such as -e key "" and -d "", and accepted input that am
start then rejects. Pass empty arguments through, and explain a failed
launch when launch_args has an empty element. Reject NUL characters,
which spawn cannot pass, with a user error.
Poll serve-sim's event log and reset the existing idle timeout when a
new preview input event appears.
Co-authored-by: Claude Opus 5.5 <[email protected]>
* [eas-cli] Add a checkout prompt experiment to the Free plan build limit error
* [eas-cli] Reuse the account billing URL helper in the checkout experiment
* [eas-cli] Add simulator:action command
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Fold simulator actions into one table
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Give the simulator API lookup its own timeout
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Drop event-log from simulator:action
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Rename to simulator:control and add sidebar actions
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Drive simulator:control from the serve-sim action catalog
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Fix value order, upload cleanup and output handling in simulator:control
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Check output paths and local files before simulator:control runs
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Upload only when the catalog condition matches
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Send upload IDs and JSON lists from simulator:control
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* [eas-cli] Complete the simulator control session fixture
Co-authored-by: Codex <[email protected]>
* [eas-cli] Close simulator control after discovery failure
Co-authored-by: Codex <[email protected]>
* [eas-cli] Keep simulator action descriptions on one line
Co-authored-by: Codex <[email protected]>
* [eas-cli] List simulator actions by default
Co-authored-by: Codex <[email protected]>
* [eas-cli] Reject empty simulator control session IDs
Document the separator for values beginning with --.
Co-authored-by: Codex <[email protected]>
* [eas-cli] Clarify local screenshot output usage
Co-authored-by: Codex <[email protected]>
* [eas-cli] Compact simulator action discovery and add action help
---------
Co-authored-by: Claude Opus 5.5 <[email protected]>
Co-authored-by: Codex <[email protected]>
* [eas-cli] Add experimentation client
* [eas-cli] Document experimentation context order and override semantics
* [eas-cli] Take the account unit from the command instead of the app config
* [eas-cli] Skip experiments in CI
* [eas-cli] Make the GraphQL request timeout take effect
* [eas-cli] Document which experiment units are shared across surfaces
* [eas-cli] Test that non-timeout fetch errors pass through the timeout wrapper
* [eas-cli] Fetch the experimentation config lazily on first variant read
* [eas-cli] Cap the actor lookup in the experimentation context field
* [eas-cli] add --frame-ancestor to simulator:start and print the embed URL
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* [eas-cli] cover the embed output fallbacks
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* [eas-cli] format the embed output tests
Co-Authored-By: Claude Fable 5.1 <[email protected]>
---------
Co-authored-by: Claude Fable 5.1 <[email protected]>
# Why
Google Play submissions sometimes fail with generic errors like `Precondition check failed.` (HTTP 400, `FAILED_PRECONDITION`). We currently drop everything except `error.message` and `errors[].reason`, so neither the user nor we can tell what Google actually objected to.
This replaces #4650, which also put Google's details into user-facing messages and structured logs, and added a redacting sanitizer. That made the code a lot more complex. This PR keeps build logs unchanged and only makes the raw response available in Sentry. Once real payloads show up there, we can add targeted classifiers to `mapGooglePlayError` with clear user-facing messages.
# How
- `GooglePlayApiError` now keeps:
- the JSON error response body, as a string capped at 8 KB
- the request URL path, without the query (the upload session query contains a secret)
Non-JSON bodies are still dropped, as before.
- `GooglePlayApiError.getErrorMetadata()` finds the API error in the cause chain, through retry `AggregateError`s and commit-outcome-unknown wrappers. It returns `googlePlayRequestPath` and `googlePlayErrorResponse`.
- `mapGooglePlayError` and `GooglePlayCommitOutcomeUnknownError` attach that as `ExpoError.metadata`. The worker already sends it to Sentry as `extras.errorMetadata`, and it is not part of the external build error.
- The body is stored as a string because `@sentry/node` 7 normalizes extras to depth 3, so nested `details` would otherwise show up as `[Object]`.
User-facing messages are unchanged.
# Test Plan
- New tests in `GooglePlaySubmission.test.ts`:
- a `FAILED_PRECONDITION` commit with `details` ends up in metadata but not in the message
- metadata survives retries when the commit outcome is unknown
- the upload-session query and non-JSON bodies are not stored
- `yarn test src/steps/utils/android src/steps/functions/__tests__/submitToGooglePlay.test.ts` (153 passed), plus `yarn typecheck`, `yarn lint`, `yarn fmt:check`
🤖 Generated with [Claude Code](https://claude.com/claude-code)
# Why
While testing submissions on staging I found Google APIs flake sometimes.
# How
Wrapped requests with auto-retry when we can be sure we can retry.
# Test Plan
CI should pass.
* [eas-cli] Show EAS Simulator minutes in eas account:usage
* [eas-cli] report unavailable Simulator usage estimates
* [eas-cli] Replace Simulator usage changelog entry with changeset
<!-- Add a changeset with `yarn changeset`, or skip the check by labeling the PR with "no changelog". -->
# Why
Now that we're testing out permission scoping for tokens, EAS CLI needs to handle these cases more gracefully. First step is this error message, which previously assumed scoped tokens would only be used within build jobs.
# How
Update it to have a separate error message for scoped tokens outside of a build job. Also correct "user"/"account" terminology discrepancy.
# Test Plan
`yarn start`
`export EXPO_STAGING=1`
`neas login`, select viewer scope
run `neas update`
see
```
You don't have the required permissions to perform this operation.
This can sometimes happen if you are logged in as incorrect user or if the permissions granted during authentication are insufficient to perform the operation.
Run eas whoami to check the user you are logged in as and your permission grant.
Run eas login to change the user or permission grant.
Original error message: Entity Not Authorized: Entity not authorized: AppFingerprintEntity[00000000-0000-0000-0000-000000000000] (viewer = ScopedAccountActorViewerContext[RegularUserViewerContext[b99c08be-7584-4358-b8e4-aef050972708], scopes=expo_account:c344bcd9-c79d-4c0b-96fb-940d947cac42(RUN,VIEW);expo_account:55ebf7e2-f986-4b54-950d-55d38f355e29(RUN,VIEW)], action = CREATE, ruleIndex = -1)
Request ID: 410d2f30-c4fa-4575-b21a-6012f6c1e93f
```
* [build-tools] Call the device run session worker API with the session token
When a device run session job has the EAS_DEVICE_RUN_SESSION_TOKEN environment
secret, send every session-related www call to /v2/device-run-session-worker/*
with the expo-device-run-session-token header instead of GraphQL or the
account-wide REST routes. Without the token, keep the current calls.
The worker also reports Datadog metrics for these jobs through
/v2/device-run-session-worker/metrics.
* [build-tools] Download session builds without the robot token
In a device run session job with a session token, the build archive URL comes
from the device run session worker API and points to an artifact route that
needs no auth. After www stops minting EXPO_TOKEN for session jobs,
robotAccessToken is the session token, and www rejects it as a bearer
credential on every route. Send no Authorization header in that case.
* [build-tools] Match the device run session worker API response contract
www returns entity values from the worker API: session statuses are
lowercase and hyphenated, and GET /application returns
{ platform: 'ios' | 'android', build: { id, gitCommitHash,
applicationArchiveUrl } | null } without app slugs. Map the statuses to the
GraphQL values that callers compare, and name screenshots without an app
slug in worker API mode.
The worker now resolves duplicate EAS_DEVICE_RUN_SESSION_TOKEN secrets like
the build env does (the last one wins), so metrics and steps use the same
token. Add tests for the token propagation from job secrets to the worker API
client and for the download_build and start_agent_device_session call sites.
* [build-tools] Take the device run session platform from the worker runtime
* [build-tools] Report device run session build lookups as system errors and time out hung session requests