fastlane snapshot failed on release scheme: simulator failed to boot error

Not specified by the original author.

TL;DR

Give snapshot a simulator it can actually boot: pick an available device type and OS runtime installed on the machine, delete corrupt simulator devices, and boot it once manually before the lane. Snapshot failures at boot are environment problems: the configured device was removed by an Xcode update, the runtime is missing, or CoreSimulator is wedged with too many stale devices. Align the Snapfile device list with simctl output and retry.

simulator failed to boot - fastlane snapshot on release scheme

Use this when

• fastlane snapshot fails early with simulator failed to boot.
• Xcode was updated and old runtimes disappeared.
• The Snapfile names devices from a previous project.

Not for this skill when

• Screenshots themselves look wrong after a successful boot. That is a UI or content problem later in the lane.
• The app crashes in the simulator during snapshot. Boot succeeded; debug the app crash instead.

Steps

1. List available simulators with the simctl list devices command and note which named devices and runtimes actually exist. Verify: the available device and runtime list is captured
2. Compare it with the devices array in the Snapfile and remove or replace every entry that is not available. Verify: Snapfile devices all appear in the simctl available list
3. Boot one target simulator manually from the command line and wait until it reports booted. Verify: simctl reports the device state as Booted
4. If boot hangs, shutdown all simulators and delete unavailable or corrupt devices, then recreate a fresh device for the needed runtime. Verify: a freshly created device boots successfully
5. Run snapshot for a single device and language first to validate the environment cheaply. Verify: one device completes its screenshot set
6. Run the full snapshot lane for the release. Verify: all configured devices finish and the screenshots folder is populated
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

snapshot drives real simulators through CoreSimulator, which depends on installed runtimes and device records that Xcode updates routinely invalidate. A device name that existed last release may be gone now, and the failure surfaces as a boot error rather than a clear missing-device message. Verifying with simctl separates environment health from lane configuration.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

fastlane snapshot simulator failed to boot fix

Lane phrasing; align Snapfile with simctl. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

CoreSimulator failed to boot device snapshot CI

CI phrasing; pre-boot a device in the job before snapshot. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: too many simulators on CI

Accumulated devices slow CoreSimulator drastically. Prune devices in the CI setup step. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_oM3efeoJqvUzwyNNQTmJHQ

Resolved from the public thread: https://vectle.com/posts/pst_oM3efeoJqvUzwyNNQTmJHQ

Thread query: fastlane snapshot failed on release scheme: simulator failed to boot error

TL;DR: Give snapshot a simulator it can actually boot: pick an available device type and OS runtime installed on the machine, delete corrupt simulator devices, and boot it once manually before the lane. Snapshot failures at boot are environment problems: the configured device was removed by an Xcode update, the runtime is missing, or CoreSimulator is wedged with too many stale devices. Align the Snapfile device list with simctl output and retry.

Not specified by the original author.

TL;DR

Walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

fastlane supply failed "Google Play API error: invalid request, release notes cannot exceed 500 characters"

Use this when

• You see this exact message or symptom in fastlane: fastlane supply failed Google Play API error: invalid request, release notes cannot exceed 500 characters
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• fastlane fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the lane and its options, the signing or metadata files the lane reads, and the API credential the lane authenticates with, and check the hand off where the test record stopped, the condition or field it failed, and the log line added there. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Verify: the corrected value or setting is visible in fastlane itself, not only in a local config file
4. Re-run the original operation on the single affected item first: run the same lane with verbose logging for one build, fix the named input, then re-run the lane end to end. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the lane finishing and the build or metadata appearing in the portal with the expected version and build number. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

fastlane supply failed Google Play API error: invalid request, release notes cannot exceed 500 characters

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

fastlane version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does fastlane supply failed Google Play API error: invalid request, release notes cannot exceed 500 characters keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: fastlane 2.220 or later, Ruby 3, App Store Connect API or Play Developer API credentials. The steps assume you can read the job or build log and change the named object in fastlane.

Why it happens

In fastlane, this failure usually means one step in the chain checks a condition or a field that the earlier steps no longer produce, so the chain stops silently at that check. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_TZcvycdY6SBEUUHfjco-JA

Resolved from the public thread: https://vectle.com/posts/pst_TZcvycdY6SBEUUHfjco-JA

Thread query: fastlane supply failed "Google Play API error: invalid request, release notes cannot exceed 500 characters"

TL;DR: Walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Start in the fastlane run log, the Fastfile and Appfile, and the store portal the lane targets, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Point frameit at frame images whose file names and device identifiers match your screenshot devices, or let frameit download the current frame set. frameit matches screenshots to frames by device name in the Framefile and the frames folder; a renamed device, a new phone generation, or a custom frames path with old assets produces device frame not found. Update the Framefile entries and frame files for the exact devices your screenshots came from.

device frame not found - fastlane frameit

Use this when

• frameit fails naming a device it cannot find a frame for.
• Screenshots were taken on a newer device generation than the stored frames.
• The frames folder was copied from another project.

Not for this skill when

• Screenshots themselves are the wrong size for the store. Framing cannot fix source resolution problems.
• You do not need framed screenshots. Skip frameit and upload raw screenshots instead.

Steps

1. Read the exact device name frameit reports missing, character for character. Verify: the missing device identifier is captured from the log
2. List the frame files available in your frames folder and the devices named in the Framefile configuration. Verify: available frames and configured devices are listed side by side
3. Download the current official frame set or add the frame image for the missing device, named exactly as frameit expects. Verify: the frame file for the device exists with the expected name
4. Correct the Framefile device entries and any custom frames path to match the real locations. Verify: the configuration points at the folder containing the new frame
5. Run frameit on one screenshot set first. Verify: one device set frames successfully with correct borders and title placement
6. Run the full frameit step for all devices and languages. Verify: all sets complete and framed images appear in the output folder
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

frameit is a matching exercise between three names that must agree: the simulator device that produced the screenshot, the device entry in the Framefile, and the frame artwork file. Device generations change yearly and names are not forgiving of a single character difference, like a missing Pro or a size suffix, so the match fails even when everything looks approximately right.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

frameit device frame not found fix

Direct phrasing; supply the exact-named frame file. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

fastlane frameit Framefile device missing

Configuration phrasing; align Framefile, frames folder and screenshot device. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: custom marketing frames

Branded frames must keep the exact screen cut-out coordinates. Test one screenshot before batch-framing a release. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_rchg9GzJnjCrldwhq-3ulA

Resolved from the public thread: https://vectle.com/posts/pst_rchg9GzJnjCrldwhq-3ulA

Thread query: fastlane frameit failed: "device frame not found" error for screenshots troubleshooting

TL;DR: Point frameit at frame images whose file names and device identifiers match your screenshot devices, or let frameit download the current frame set. frameit matches screenshots to frames by device name in the Framefile and the frames folder; a renamed device, a new phone generation, or a custom frames path with old assets produces device frame not found. Update the Framefile entries and frame files for the exact devices your screenshots came from.