Add GeneratedDotEnv.m as an output file #751
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
Locally I can build my app just fine, but when I do:
the subsequent builds fail, and the only way they succeed again is if I clear the DerivedData folder before building.
This is the output when I build after nuking my node_modules folder:
So this actually makes sense — the ruby script to produce GeneratedDotEnv.m doesn't get re-ran because its inputs/outputs didn't change, but that's because GeneratedDotEnv.m isn't part of the inputs or outputs.
What
This PR adds the GeneratedDotEnv.m to the outputs of the build script that produces it, so that it gets regenerated when necessary.