Cloudinary will not build

[darkmantle]

I am using CocoaPods, setup exactly how suggested in the documentation, but 2 things happen.

First it requires 9.0 platform (docs say 8.0) and secondly whenever building it says "No such module CLDCrypto" despite the module actually being within the code.

[tocker]

Hi @darkmantle,
Thanks for trying the new code!
The CLDCrypto module was supposed to be created during the installation of the pod.
We're investigating this issue.

[tocker]

Can you please verify that the following path exists under the root of your project?

Pods/Cloudinary/Cloudinary/Frameworks/CLDCrypto/

If it does, please try changing the Framework search path from ./Cloudinary/Frameworks/CLDCrypto/ to ./Cloudinary/Cloudinary/Frameworks/CLDCrypto/ (see photo below). If this works, I'll modify the build script accordingly.

[meandkareem]

I have same issue .. where should I change this path ? this is generated via cocapods $inherited so I cant change it in Xcode

[darkmantle]

Sorry, it did work, i just edited the wrong build settings!

As of right now I can build and use the app, with Cloudinary imported.

Cheers.

[darkmantle]

However now there are warnings saying "Directory not found for option '-FCloudinary/Cloudinary/Frameworks/CLDCrypto/iphoneos'" which is annoying. Does not stop the app working but just so you know!

[chrisellsworth]

Those who don't have Pods/ in source control might find something like the following addition to Podfile to be useful:

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      # remove this when https://github.com/cloudinary/cloudinary_ios/issues/57 is resolved
      if target.name == 'Cloudinary'
        config.build_settings['FRAMEWORK_SEARCH_PATHS'] = [
          '$(inherited)',
          './Cloudinary/Cloudinary/Frameworks/CLDCrypto/$(PLATFORM_NAME)',
          '$PODS_CONFIGURATION_BUILD_DIR/Alamofire'
        ]
      end
    end
  end
end

[darkmantle]

@chrisellsworth Worked perfect for me

[tocker]

Hi All,

The issue was in the way pod lib lint works vs. pod install.
Please try version 2.0.1. It should build correctly 🙏 .
You will get the following linker warning which you can safely ignore:

ld: warning: directory not found for option '-FCloudinary/Frameworks/CLDCrypto/iphonesimulator'

Please let us know if this solved you issue!

[chrisellsworth]

It builds! Thanks @tocker!

[wouterBouwmeester]

I have kind of the same issue:

I am able to build to any device, but when I try to Archive I get:
ld: warning: directory not found for option '-FCloudinary/Frameworks/CLDCrypto/iphoneos'
ld: framework not found Pods_Campground_App
clang: error: linker command failed with exit code 1 (use -v to see invocation)

This causes the Archive to fail.

I tried to fix this by updating to 2.0.1, but after updating the error changes to:
ld: warning: directory not found for option '-FCloudinary/Cloudinary/Frameworks/CLDCrypto/iphoneos'
ld: framework not found Pods_Campground_App
clang: error: linker command failed with exit code 1 (use -v to see invocation)

The Framework search path was wrong after the update so I changed it to: "./Cloudinary/Cloudinary/Frameworks/CLDCrypto/$(PLATFORM_NAME)"

but then the error got back to:
ld: warning: directory not found for option '-FCloudinary/Frameworks/CLDCrypto/iphoneos'
ld: framework not found Pods_Campground_App
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I noticed that the xcconfig files still had Cloudinary/Frameworks, but even after those to Cloudinary/Cloudinary/Frameworks I still get the same error.

I searched all files in my project for "Cloudinary/Framework" and noticed that it occurs in UserInterfaceState.xcuserstate, but when i delete this file Xcode generates a new file with the same wrong path.

Edit:
I got it working by removing Cloudinary pod and the original target. After adding a new target i was able to add Cloudinary and archive again.

[paulhimes]

Version 2.0.1 is still putting a duplicate reference to the wrong directory in the Framework Search Paths and the Import Paths:

$(PODS_ROOT)/Cloudinary/Cloudinary/Frameworks/CLDCrypto/$(PLATFORM_NAME)
./Cloudinary/Frameworks/CLDCrypto/$(PLATFORM_NAME)

[roeeba]

Hi @paulhimes. I apologise for the delayed reply. While I'm not sure it's still relevant to you, some CLDCrypto issues were solved in 2.0.2 so this may already be fixed. That said, please let us know if you're still seeing an issue, and we'll gladly help further.

[marcospolanco]

This is still broken in 2.0.2. I had to change the '11.0.sdk' to '11.1.sdk' to make it work.

[roeeba]

Hi @marcospolanco, please refer to the following thread for possible workarounds - #107

And to this comment in particular -
#107 (comment)

[roeeba]

Closing this issue due to the time elapsed. Please feel free to either re-open the issue, contact our support at http://support.cloudinary.com or create a new ticket if you have any additional issues.