Question or problem
Hi everyone, I’ve run into a persistent issue with Tuist and wanted to check
if anyone in the community has experienced something similar or has insights.I’ve already filed a bug report on Github.
I’m sharing it here to get more visibility and explore potential workarounds
while waiting for a resolution.I’m trying to use ProjectDescriptionHelpers to centralize the creation of
custom schemes and configurations for my project. My goal is to follow the
‘Don’t Repeat Yourself’ principle.I’ve confirmed that the configuration names (Debug, Staging, Production) are
identical to those referenced by the schemes. My project and helper code are
logically consistent. I have made sure to only use the.debugand.release
variants for Settings.Configuration. And I’m using a Workspace.swift with automaticSchemesOptions: .disabled to manually manage my schemes.Yet when I run
tuist generate, I consistently
get the error:The build configuration 'Staging' specified in the scheme's run action isn't defined in the project.I’ve already ruled out:
- Typos: The configuration names match exactly.
- Incorrect Paths: xcconfig file path is relative to the workspace root.
This is my first time using a project generation tool like Tuist, so it’s
very possible my mental model is off regarding how configurations should be
resolved.I’m looking for any insights or workarounds the community might have. Has
anyone else experienced this, and if so, how did you handle it?"You can find the reproducible repo here.
Expectation
If an issue: Tell us what you were expecting
If a how-to: Tell us how you’d have expected Tuist to help you
Context
- Tuist version: x.y.z
Give us some context on what you were trying to do when you stumbled upon the need to create this topic in the community forum.
Reproduction (mandatory for problems)
Include a reproducible project and steps to reproduce the issue. If you have logs, include them too.