Skip to main content

UBA build fails with "Error: The handle is invalid Checkout failed: Failed to create new workspace"

Updated

A user returned to an older DevOps/Unity Build Automation setup and found all builds failing when Plastic SCM tried to create a workspace, showing “The handle is invalid” and failing before builds started. Investigation showed an outdated or broken connection between Unity Build Automation and the Unity Version Control (Plastic SCM) repository. Refreshing the Source Control connection in the Unity Dashboard resolved the issue, and an optional migration from a legacy Plastic SCM subscription to the new DevOps subscription was recommended.

 

Symptoms

  • Builds fail when Plastic SCM tries to create a workspace with the error: “The handle is invalid”.
  • Checkout fails with “Failed to create new workspace”.
  • Build fails before starting when reading from projectSettings.txt.
  • Repository appears correctly connected and accessible via the organization's site, and local work is fine, but builds are completely blocked.

Causes

An outdated or invalid connection configuration between Unity Build Automation (Unity DevOps) and the Unity Version Control (Plastic SCM) repository, likely due to changes in Plastic SCM/Unity Version Control services and authentication over time. The build pipeline was still using legacy or stale connection settings, causing authentication or workspace-creation failures when Unity Build Automation attempted to access the repository.

 

Resolution

  1. Open the Unity Dashboard and navigate to DevOps > Settings > Source Control.
  2. Temporarily switch the Source Control provider to another provider (e.g., GitHub), then click Save.
  3. Switch back to Unity Version Control and choose the Custom option.
  4. Select the appropriate organization server (for example, <OrgName>@cloud).
  5. Choose Authenticate with Unity ID.
  6. Save the settings, then re-save the build target configuration.
  7. If issues persist or to future‑proof the setup, migrate repositories from the legacy Plastic SCM/UVCS subscription to the new DevOps/Version Control subscription using the official transfer guides below.
  8. After migration, reconnect Source Control in the Unity Dashboard by selecting Unity Version Control, choosing the Default option, and saving.
     

More Information

For more information about migrating repositories, please visit the following articles:


[Repositories / Projects] Transfer a repository from cloud repo to cloud repo using GUI app

[Repositories / Projects] Transferring Repositories Between UVCS/Plastic SCM (Legacy) Organizations to Unity Organizations

Related to

Related articles