Removed: BDC9821B1E9BD1B600ADE0EF /* (null) in Sources */ = {isa = PBXBuildFile; };
Added: BDC9821B1E9BD1B600ADE0EF /* BuildFile in Sources */ = {isa = PBXBuildFile; };
I hope this can help,
Regards.
–
–
–
–
This is a known issue with Swift 4.2 and Xcode 10. I found an article here that fixed it for me: https://github.com/Yummypets/YPImagePicker/issues/236
In short, go to your projects build settings, and add a user defined setting named SWIFT_ENABLE_BATCH_MODE and set its value to NO.
Previously, I tried each of the following methods suggested elsewhere (rebuild, exit Xcode, clean and rebuild, purge Derived Data files). None of them worked.
Once I added the user define build setting per the article, Swift then told me the true error. In my case, it was a missing }, but it could be any number of problems.
–
My problem was I had due to the non-existence of a native Swift CommonCrypto, used a bridging header and a target that with some magic included it in the build. Since CommonCrypto is now native, I solved the problem by removing the target and the #import and instead added an import CommonCrypto where I used it.
–
–
–
Open Xcode Preferences (Command,)
Go to the Locations tab
Click on the small gray arrow which shows URL path for Derived Data
The finder window will open up and show the following folders:
DerivedData
Archives
iOS DeviceSupport
UserData
DocumentationCache
iOS Device Logs
Quit Xcode
Delete the DerivedData folder (it just contains a cache from previous builds)
Restart Xcode
- Go to build settings
- Search SWIFT_COMPILATION_MODE
- If this is "Whole Module" for Release configuration then change it to "Incremental".
- Archive now.
When you change the setting to "Incremental" the process succeeds.
Mine was a name spacing issue. I had two files with the same name. Just renamed them and it resolved.
Always gotta check the 'stupid me' box first before looking elsewhere. : )
Let me share my experience for this issue fix.
Open target -> Build phases -> Copy Bundle Resources and remove info.plist.
Note: If you're using any extensions, remove the info.plist of that extension from the Targets.
Hope it helps.
–
It seems like this is a pretty vague error, so I will share what I did to fix it when I ran into this:
Using Xcode 10.1 and Swift 4.2 I tried pretty much all the suggestions here but none of them worked for me, then I realized a dependency I was using was not compatible with Swift 4.2 and that was causing me to get this error on other pods. So to fix it I just had to force that pod to use Swift 4.0 by putting this at the end of my Podfile:
post_install do |installer|
installer.pods_project.targets.each do |target|
if ['TKRadarChart'].include? target.name
target.build_configurations.each do |config|
config.build_settings['SWIFT_VERSION'] = '4.0'
I searched the whole web but I couldn't find any solution for this problem. I managed to REMOVE the "Common Crypto" path in the section: IMPORT Paths in Build settings.
The problem seems to be that "common crypto" now exists in the foundation in the ios 12 sdk.
Simply remove the path for file "common crypto" in the build settings and the project will build like a charm! :)
–
Just adding to this question. My issue didn't have anything to do with CommonCrypto. It created a new Single App application and tested to run. Compiler was complaining about using Swift 4.2
Changing the Swift language to version 4.0 in Build settings fixed the issue. Not sure if this is a bug.
I got this randomly since Xcode 10. I think it occurs when I change something in the code while building starts.
The next build works every time.
I also encountered the same issue and I did what @cdeerinck suggested and got to the following link which suggested adding a user-defined variable to the Build Settings to disable batch mode i.e. add a new user defined variable named SWIFT_ENABLE_BATCH_MODE and set it to NO, I was able to get more insights into the issue and I got to know that the error was in a framework using CommonCrypto which was added to it(by me) but since Xcode 10 it is exposed natively as part of Swift (for Apple platforms only), and adding it (or its existence from the previous version) was causing a name collision and hence it was throwing the error. To know more refer to the this link which explains the issue in more detail.
I have the same issue and my solution is change a little thing in Build Settings
SWIFT_COMPILATION_MODE = singlefile;
SWIFT_OPTIMIZATION_LEVEL = "-O";
