XcodeGen VS SwiftGen

Worth noting if project file changes would be pretty common in the development flow then maybe using a regen tool would be useful to prevent major conflicts, I’d recommend https://github.com/yonaskolb/XcodeGen

There are a lot of tools and solutions that can help manage a large codebase. For example, a good CI/CD system linked to GitHub or your internal source control system can ensure that all of your unit tests and UI tests run on every PR and block PRs from merging if there are test failures. And if the company chooses not to check in the .xcodeproj or .xcworkspace file, but rather rely on project autogeneration tools like xcodegen, then you can eliminate annoying merge conflicts in PRs that happen when two teams happen to touch files that are near each other in the .pbxproj file (but at the cost of developers always having to run xcodegen when checking out a new branch).

`git clone https://github.com/yonaskolb/XcodeGen.git cd XcodeGen make install`

Parent comment is right, but check out XcodeGen and get away from the project file. It’s an abomination.

I don't see anything wrong with your gitignore. If this is causing too many problems, have you considered using a tool that will generate xcodeproj files for you, like XcodeGen?

Curious why you guys built XCodeJS instead of going with XcodeGen or Tuist

It's such trash. For my personal projects, XcodeGen is a lifesaver.

How Apple thinks that a single god file is a good idea is crazy to me. No other build tool needs this.

https://github.com/yonaskolb/XcodeGen

It is important to say that there is an elegant solution to the resource consistency problem that we haven’t adapted yet. Instead of testing raw values of UIStoryboard.Name cases, we could just generate the UIStoryboard.Name enum. Please refer to SwiftGen for the details.

Your strings should work as-is if you use a tool like SwiftGen (it generates compiler-enforced types for use in your app).

Tools like https://github.com/SwiftGen/SwiftGen can be used to ensure at compile time that all keys used in your app are actually defined. Having keys organized as hierarchical enums, with auto-completion in Xcode is also a nice plus.

Our project includes a Gemfile which we use to specify some external dependencies. I'm trying to add SwiftGen (https://github.com/SwiftGen/SwiftGen) to the project. We want to eventually deprecate Cocoapods so I can't use that installation method.

https://github.com/SwiftGen/SwiftGen/issues/627#issuecomment-715259788

Or you can use something like SwiftGen and have code generation for your localized strings and have it checked at compile time instead of getting those pesky typo errors at runtime that you never check ;)