Xcode 6.4: Opening a file containing an @import statement will show "Could not build module" error
| Originator: | luc-olivier.dumais-blais | ||
| Number: | rdar://22273887 | Date Originated: | 13-Aug-2015 03:34 PM |
| Status: | Open | Resolved: | |
| Product: | Developer Tools | Product Version: | Xcode 6.4 (6E35b) |
| Classification: | Other Bug | Reproducible: | Sometimes |
Summary: Opening an Objective-C source file that contains an @import statement sometimes fails with an error (“Could not build module ‘X’). This error does not show up when you try to build the currently selected target. Steps to Reproduce: 1. Search for a source file that contains @import in your codebase. 2. Open a file in the search results. Expected Results: The file opens without any error. Actual Results: The file opens and there is an error at the line of the @import statement. Notes: This seems to happen only with 3rd-party modules. I have yet to seen it with Apple-provided modules. Also, this error is more frequent unit test source files.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!