Bot shows build errors for swift files that were moved, but still creating archive
| Originator: | pratikvarma | ||
| Number: | rdar://22368982 | Date Originated: | 8/20/2015 |
| Status: | open | Resolved: | |
| Product: | Xcode | Product Version: | 6.4.1 |
| Classification: | Developer tools | Reproducible: | Sometimes |
Summary: I recently moved around some swift files in my project for better organization. This changed the .xcproj file. On building, my Xcode integration bots shows the following kind of swift errors: Bot Issue: error. Swift Compiler Error. Issue: Use of unresolved identifier 'MySwiftClass'. File: MtSwiftClassUser.swift. Integration Number: 224. Integration URL: https://xcodebotserver/xcode/bots/D6BF719/integrations Description: Use of unresolved identifier 'MySwiftClass'. Committers: Introduced 10 integrations ago. However the bot did create an archive. We've tried cleaning the project, deleting derived data etc. but it does not seem to help. Steps to Reproduce: 1. Create a project with swift files. Add to source control. 2. Create new Groups and move files physically to new folders on file system. 3. Verify that a diff on the project shows that file locations have changed. Commit updates to source control. 4. Close Xcode and open project again. Expected Results: Moving files around should not really matter. If a swift file uses a swift class in a moved file, it should be able to locate it. Actual Results: Symbol table gets corrupted. Swift code with references to the moved code shows errors. Version: 6.4.1 & 10.10.4 Notes: Related issue: http://swift-error.com/ios/swift-xcode-autocomplete-stopped-working-symbol-not-found/ used following steps to mitigate: 1) rm -r ~/Library/Caches/com.apple.dt.Xcode 2) restart Xcode Configuration: Attachments:
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!