7

I have razor pay pod in my project for payment gateway and SWRevelViewController file for side bar controller. I selected the swift 5 and iOS version 13 and updated all the pods but still getting error

error: using bridging headers with module interfaces is unsupported Command CompileSwiftSources failed with a nonzero exit code

pod 'Alamofire', '~> 4.5' pod 'TWMessageBarManager'
pod 'SwiftValidator', :git => 'https://github.com/jpotts18/SwiftValidator.git', :tag => '4.2.0'

pod 'SDWebImage', '~> 5.0'
pod 'DropDown'
pod 'MBRadioCheckboxButton'
pod 'SwiftyJSON', '~> 4.0'
pod 'razorpay-pod', '~> 1.1.1'
pod 'GoogleMaps'
pod 'GooglePlaces'
pod 'Firebase/Auth'
pod 'SVProgressHUD'     
pod 'FacebookLogin'
pod 'FacebookCore'
pod 'ImageSlideshow', '~> 1.8.0'
pod "ImageSlideshow/SDWebImage"
pod 'Firebase/Core'
pod 'Firebase/Messaging'
pod 'PopupDialog', '~> 1.1'
pod 'GoogleSignIn'
pod 'AppAuth','~> 1.2.0'
aturan23
  • 4,798
  • 4
  • 28
  • 52
sagarmahi onwork
  • 87
  • 1
  • 1
  • 7

5 Answers5

11

In my case, i had to follow these steps:

Step 1:

config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'NO'

in my Podfile under

...

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
    target.build_configurations.each do |config|
      # Put it here (indent like this)
  ...

Step 2

  • Select Runner on the left Panel
  • Under Targets, select the target (usually "Runner")
  • Select Build Settings from the top Menu
  • Scroll down to Build Options and find the option "Build Libraries for Distribution"
  • Set the value of "Build Libraries for Distribution" to NO (or set it for any particular build scheme)
  • Clean Build Folder
  • Delete flutter "build" folder, run flutter clean & flutter pub get
Brendan
  • 910
  • 1
  • 14
  • 32
5

I checked your problem and as per you selected project language project work properly in XCode 10.2 but you require changes for updated XCode 11.2.1

Please follow few things :

  1. Make sure first your bridging header file path is proper in build settings.
  2. You need to update razor pay pod because you add tag (pod 'razorpay-pod', '~> 1.1.1'), and pod updated in Swift 5.1 so please remove it and change pod name with pod 'razorpay-pod'
  3. Please change your build settings. Set Build Library for Distribution in the build settings for the target framework to YES.

Hope it’s helpful to you.

Anjali Shah
  • 720
  • 7
  • 21
0

This is a similar question (same exact error message) to Xcode 11.2.1 error: Command CompileSwiftSources failed with a nonzero exit code.

I posted an answer that can be found here.

Hope it works for you!

Tony Xu
  • 194
  • 2
  • 9
  • sorry, but I'm not sure how else to help. Was there anything specific you observed in terms of errors or otherwise that you can share? I'll try my best to help. – Tony Xu Mar 17 '20 at 17:53
0

So I faced a problem with Razorpay swift version and following one of the suggested methodologies set Target>Build Libraries for Distribution to Yes.

Big mistake.

kept getting error: using bridging headers with module interfaces is unsupported

Finally fixed it by setting Build Libraries for Distribution Back to No [Razorpay issue was still not resolved so had to downgrade Flutter]

ActivX
  • 1
  • This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://stackoverflow.com/questions/ask). To get notified when this question gets new answers, you can [follow this question](https://meta.stackexchange.com/q/345661). Once you have enough [reputation](https://stackoverflow.com/help/whats-reputation), you can also [add a bounty](https://stackoverflow.com/help/privileges/set-bounties) to draw more attention to this question. - [From Review](/review/late-answers/30426723) – Runt8 Nov 27 '21 at 15:56
-1

I have solved it in this way, Detailed steps are here, Solution to Xcode Error: using bridging headers with module interfaces is unsupported

Solution:

In your Project Level & Target level Build Settings tab, open the Build Options menu. And then set Build Libraries for Distribution option to No.

Asad Ali Choudhry
  • 4,985
  • 4
  • 31
  • 36
  • 7
    The accepted answer says to set it to **YES**. This is confusing.. – Sti Nov 23 '20 at 10:25
  • Not a solution. Plus, you're posting a link to your own blog or whatever instead of answering the question in here. – Yoshimitsu Jun 16 '21 at 20:57
  • It is not a solution as if you need to prepare the lib for distribution you need to have this option as YES – Sirop4ik Aug 24 '21 at 07:20