Xcode warning: “no rule to process file” #938

Activity

1. fumoboy007

   added

   kind/bugFeature doesn't work as expected.Feature doesn't work as expected.

   status/triageCollecting information required to triage the issue.Collecting information required to triage the issue.

   on Aug 18, 2026
2. simonjbeaumont commented on Aug 18, 2026

   

   simonjbeaumont

   on Aug 18, 2026

   Collaborator

   More actions

   Assuming you have the build plugin enabled for your target, then these files are used and any warning in Xcode that they are not is an Xcode bug. It sounds like these are cosmetic and your project builds successfully? If you would like to see these warnings addressed you will probably need to file an issue with Feedback Assistant, for Xcode.

   I don't know much about Xcode project file structure, but wonder if this is meaningful:

   /* Begin PBXFileSystemSynchronizedGroupBuildPhaseMembershipExceptionSet section */
                   E6AC3B73303412A100AFB1E0 /* Exceptions for "OpenAPIGenerator-NoRuleToProcessFileWarningRepro" folder in "Compile Sources" phase from "OpenAPIGenerator-NoRuleToProcessFileWarningRepro" target */ = {
                           isa = PBXFileSystemSynchronizedGroupBuildPhaseMembershipExceptionSet;
                           buildPhase = E67A5277303410980009054A /* Sources */;
                           membershipExceptions = (
                                   "openapi-generator-config.yaml",
                                   openapi.yaml,
                           );
                   };
   /* End PBXFileSystemSynchronizedGroupBuildPhaseMembershipExceptionSet section */
   
3. simonjbeaumont commented on Aug 18, 2026

   

   simonjbeaumont

   on Aug 18, 2026

   Collaborator

   More actions

   OK, I have a workaround...

   The issue appears to be the presence of the files in the list of "Compile Sources" for the target:

   

   However, you cannot simply remove them from the list because they will not be made available to the build plugin and it will fail to run.

   A workaround I found was to go to the "Build Rules" tab (to the right of the "Build Phases" tab and add a custom rule:

   

   Use */openapi-generator-config.yaml as the matching string, use a custom but EMPTY script, and declare $(DERIVED_FILES_DIR)/nothing-to-see-here as the output file.

   Create an equivalent one for */openapi.yaml.

   When I did this, it got rid of the warnings.

   🚀React with 🚀2Reacted by Honza Dvorsky and fumoboy007
4. czechboy0 commented on Aug 18, 2026

   

   czechboy0

   on Aug 18, 2026

   Contributor

   More actions

   Wow, that's a great find, @simonjbeaumont. But yeah, @fumoboy007 please file a bug on Xcode for this, and post the FB number here please.
5. fumoboy007 commented on Aug 18, 2026

   

   fumoboy007

   on Aug 18, 2026

   Author

   More actions

   @simonjbeaumont Thanks for finding a workaround! 😃

   @czechboy0 FB24402412
6. czechboy0 commented on Sep 25, 2026

   

   czechboy0

   on Sep 25, 2026

   Contributor

   More actions

   Closing, as this was now filed through Feedback Assistant on the Xcode team. Will pin the issue for visibility.
7. czechboy0

   closed this as not plannedon Sep 25, 2026
8. czechboy0

   pinned this issue on Sep 25, 2026