Question 131615 in Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Xcode – Multiple commands produce

I just created a new project, and installed some pods. When I try to build, I get these two errors:

Showing Recent Issues
Multiple commands produce '/Users/myUser/Library/Developer/Xcode/DerivedData/Demo-eobcppugxuuucmefyvotwbqadppx/Build/Intermediates.noindex/Demo.build/Debug-iphonesimulator/Demo.build/Objects-normal/arm64/AppDelegate.stringsdata':
1) Target 'Demo' (project 'Demo') has compile command for Swift source files
2) Target 'Demo' (project 'Demo') has compile command for Swift source files


Showing Recent Issues
Multiple commands produce '/Users/myUser/Library/Developer/Xcode/DerivedData/Demo-eobcppugxuuucmefyvotwbqadppx/Build/Intermediates.noindex/Demo.build/Debug-iphonesimulator/Demo.build/Objects-normal/arm64/SceneDelegate.stringsdata':
1) Target 'Demo' (project 'Demo') has compile command for Swift source files
2) Target 'Demo' (project 'Demo') has compile command for Swift source files
Tags:

3

Answers


  1. Chosen as BEST ANSWER
    0

    Turns out I had duplicate swift files in targets -> Build Phases Deleted the ones that where duplicates, and all ok


  2. 0

    I had the same problem but in my case, I have same name for two swift files. The solution for that is Go to Targets -> Build Phases -> Compile Sources, and check whether you have the same named Swift files, and remove any one from there.

    Another issue of this error is under Targets -> Build Phases -> Copy Bundle Resources, if there are same named bundled resources, remove any one from that.

    Login or Signup to reply.
  3. 0

    For me it was a view from an app extension, which was named the same as a view from my main app. Renaming the view from the extension solved the issue.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search