You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hello! Sometimes the action fails at the post step with a next error:
Post job cleanup.
Shutting down device 4C7E3539-9231-4B19-B38F-D9D936BEC706.
$ xcrun simctl shutdown 4C7E3539-9231-4B19-B38F-D9D936BEC706
Error: Command failed: xcrun simctl shutdown 4C7E3539-9231-4B19-B38F-D9D936BEC706
An error was encountered processing the command (domain=com.apple.CoreSimulator.SimError, code=405):
Unable to shutdown device in current state: Shutdown
Several times I saw the error with the status Shutting Down
To Reproduce
I don't know how to reliably reproduce this, but it happens from time to time when running UI tests with multiple simulator clones.
Expected behavior
No error
Additional context
I think need to check status of the simulator and not call xcrun simctl shutdown if status is Shutdown or Shutting Down
Thank you for reporting! To help me assess the urgency, could you please confirm whether the error also breaks (marks as "failed") the GitHub Actions workflow, or only logs the message?
Sorry for delay, I can't find any logs to confirm that the action breaks the entire workflow if it fails at the Post step (because GitHub only stores these logs for 90 days). Currently I only have logs of failed UI tests that result in a failure simulator-action at the Post step:
Hi! Not sure this fixes the underlying shutdown-state issue, but it did for me: I was using steps.simulator.outputs.UDID and switching to steps.simulator.outputs.udid resolved it.
Activity
dotdoom commentedon Mar 8, 2025
Thank you for reporting! To help me assess the urgency, could you please confirm whether the error also breaks (marks as "failed") the GitHub Actions workflow, or only logs the message?
rock88 commentedon Mar 12, 2025
Hi @dotdoom,
Sorry for delay, I can't find any logs to confirm that the action breaks the entire workflow if it fails at the Post step (because GitHub only stores these logs for 90 days). Currently I only have logs of failed UI tests that result in a failure
simulator-actionat the Post step:Print stdout/stderr even if the command fails
Print stdout/stderr even if the command fails
nickolas-dimitrakas commentedon Feb 3, 2026
Hi! Not sure this fixes the underlying shutdown-state issue, but it did for me: I was using
steps.simulator.outputs.UDIDand switching tosteps.simulator.outputs.udidresolved it.