Networking issues prevent `tuist generate` from working when `fullHandle` is set in config

Metadata

Source

tuist/tuist #8213

Updated

Jun 11, 2026

Domains

CLI

Details

What happened?

During the brief API outage, some of our engineers reported that they were unable to run tuist generate, but not everyone.

From the logs, it seems that the cli failed to refresh their access token due to the outage and this caused an unrecoverable error.

The expected outcome is that the user should still be able to run tuist commands locally but cloud features would understandably not work or be skipped (i.e the project should generate but a run would not be reported on tuist.dev)

How do we reproduce it?

Wait for an API outage and for your access token to expire(?)
Run tuist generate --no-binary-cache

Error log

✖ Error 
  The refreshing of the access and refresh token pair for the URL https://tuist.dev/ failed after 5 seconds. 

  Sorry this didn't work. Here's what to try next: 
   ▸ If the error is actionable, address it
   ▸ If the error is not actionable, let's discuss it in the Troubleshooting & how to
   ▸ If you are very certain it's a bug, file an issue
   ▸ Check out the logs at /Users/palomaliniers/.local/state/tuist/logs/2F233D5E-0633-4F00-915D-A9E022B3B959.log

macOS version

15.6

Tuist version

4.66.1

Xcode version

26.0

Comments

D

dosubot[bot] Sep 16, 2025

This is a known issue: when cloud features are enabled (internally via the fullHandle mode), any networking or authentication failure (like an API outage or expired token) will cause tuist generate to fail, even though the actual project generation could proceed locally. This strict error handling is by design in fullHandle mode, which is not user-configurable but is set internally by Tuist when cloud features are active. The community and Tuist team agree this is not ideal—tuist generate should not fail just because the server is down, and there are suggestions for a CLI flag to skip cloud authentication so local generation can continue without cloud features. However, as of 4.66.1, there is no such flag or fallback, and recent changes do not address this behavior. For now, the only workaround is to disable cloud features if you want to guarantee local generation during outages.
See community discussion and team acknowledgment
Authentication and error handling docs

To reply, just mention @dosu.

Docs are dead. Just use Dosu.

Networking issues prevent tuist generate from working when fullHandle is set in config