A scheme available on your laptop can be absent from Xcode Cloud if it is not shared. Apple’s troubleshooting guidance calls for sharing a scheme when the workflow action cannot list it. Begin by matching the project or workspace used by the cloud workflow to the one you open locally. A similar display name can conceal two different entry points.
Match the project the cloud build opens
Write down the failing workflow, branch, commit and action. Open that exact checkout locally and choose the same workspace or project. Look for the scheme name shown in the cloud configuration. If your everyday workspace includes several projects, opening one project alone may present a different set of choices.
Suppose the team builds Workspace A locally while a new cloud workflow points to Project B. Sharing an unrelated scheme will leave the mismatch unresolved. Correct the entry point first, then review the scheme that builds the intended app. Keep the app target and test target names beside the workflow record.
Share the scheme and inspect the commit
In Xcode’s scheme management UI, locate the intended scheme and mark it Shared. Review the resulting shared scheme file in source control and commit it with the project changes it needs. Avoid assuming a local UI change has reached the cloud. Verify the committed tree at the SHA selected by the next run.
For an app that should archive, inspect the scheme’s Build action and verify the intended product participates in the Archive action. A visible scheme and an archiveable product are separate checks. If tests are missing, inspect its Test action as well. Use the configuration intended for that action, rather than changing all actions at once.
Verify the exact cloud action
Start a cloud build from the commit containing the shared scheme. Verify the log names the intended project or workspace, scheme and action. If the scheme is now found but compilation fails, follow that new error. It shows the investigation has moved beyond discovery.
As a team check, open a clean checkout on another machine and confirm the same scheme exists there. Run the relevant test or archive action. This catches local-only assumptions before another developer encounters them. The workspace example is illustrative; the procedure is based on Apple’s Xcode documentation.