UiPath Pitfall #2: Keeping Your Studio Project in a OneDrive Sync Folder

Description and use

Moving a UiPath Studio project out of a OneDrive sync folder to a local path and using Git for version control removes compile errors and cross‑machine issues.

Problem

Studio projects in OneDrive or other sync folders cause vague compile errors (Error code 1) and cross‑machine failures.

Outcome

Moving the Studio project to a local, non‑synced folder and using Git for version control removes compile errors and ensures consistent project behavior across machines.

Workflow

• 1. Move the project folder to a local path such as C:\UiPathProjects\ or a non‑synced Documents folder.
• 2. In Studio, use the Team tab → GIT Init to add the project to a local Git repository, commit, and push to a remote. (TFS/SVN also supported.)
• 3. Keep the .local folder out of source control to avoid caching issues.
• 4. For backup, zip or copy the project after closing Studio; do not develop inside the synced folder.
• 5. Verify no OneDrive sync icons appear on project.json or workflow files before publishing.

Evidence

If it's inside OneDrive or any always-sync cloud folder, that's very likely your problem.

Source

Studio writes a lot of files while you work: project.json, generated files, and a local cache in the hidden .local folder.

Source

Copy the project to a real local disk and it suddenly works.

Source

In Studio, go to the Team tab and use GIT Init to add the project to a local Git repository, commit, then push to a remote.

Source