I have included the Pod Texture in my project. I am getting errors for one file in the module but not others. I get unresolved references to types and classes. But I don't get this in other files in Texture. And these are ussages from the same file referencing the Texture module. I have Import AsyncDisplayKit at the top of the file and it does not help. What is drving me nuts is that all references are being found except the ASVideo Classes and types. Is there file level control somewhere in Xcocde for Pod inclusion?

Hi, I'm new to IOS application development and wondering if there is there a guide for integrating a IOS application in swift 5 with Texture. I have inherited an application that looks like it was using Swift 3. I get a ton of errors like NSForgroundColorAttributeName has been renamed to NSAttributedStringKey.foregroundColor. Seeing that Texture is written in Objective-C and the app is in swift it seems that there is a linkage issue. I saw somthing about these name changes coming in swift 4 so they wouldn't have had that problem when they were using swift 3. And it seems that if I want to use Xcode 13.1 and swift I need to figure how to integreate with the Texture (Objective-C) pod. There seems to be a few options here. One is to change the names, One is to figure out the linkage.Any recommendations?

Does anyone out there have a solution for finding errors that cause "Command CompileSwiftSources failed with a nonzero exit code. I see a lot of forum answers with specific solutions to their instances of this error. What I am looking for is a definitive way to find the failures. First I am amazed that apple cannot improve this. I have read a lot of threads on this issue and it seems to be there in many versions of xcode. It seems to be the cause of a great deal of frustration and I have spent a week trying to get my project (that I inherited) to compile on the latest platform (Monteray and Xcode 13.01). In my specific case I have a number of coco pods that are old versions but due to dependencies I have to use (to include MMChatFramework pod). What I am seeing is numerous pods that compile with the following error. /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -incremental -module-name DropDown -Onone -enable-batch-mode -enforce-exclusivity=checked @/Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/Objects-normal/x86_64/DropDown.SwiftFileList -DDEBUG -D COCOAPODS -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.0.sdk -target x86_64-apple-ios15.0-simulator -g -module-cache-path /Users/markp/Library/Developer/Xcode/DerivedData/ModuleCache.noindex -Xfrontend -serialize-debugging-options -enable-testing -index-store-path /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Index/DataStore -swift-version 5 -I /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Products/Debug-iphonesimulator/DropDown -F /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Products/Debug-iphonesimulator/DropDown -c -j12 -output-file-map /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/Objects-normal/x86_64/DropDown-OutputFileMap.json -parseable-output -serialize-diagnostics -emit-dependencies -emit-module -emit-module-path /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/Objects-normal/x86_64/DropDown.swiftmodule -Xcc -I/Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/swift-overrides.hmap -Xcc -iquote -Xcc /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/DropDown-generated-files.hmap -Xcc -I/Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/DropDown-own-target-headers.hmap -Xcc -I/Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/DropDown-all-non-framework-target-headers.hmap -Xcc -ivfsoverlay -Xcc /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/all-product-headers.yaml -Xcc -iquote -Xcc /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/DropDown-project-headers.hmap -Xcc -I/Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Products/Debug-iphonesimulator/DropDown/include -Xcc -I/Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/DerivedSources-normal/x86_64 -Xcc -I/Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/DerivedSources/x86_64 -Xcc -I/Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/DerivedSources -Xcc -DPOD_CONFIGURATION_DEBUG=1 -Xcc -DDEBUG=1 -Xcc -DCOCOAPODS=1 -emit-objc-header -emit-objc-header-path /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/Objects-normal/x86_64/DropDown-Swift.h -import-underlying-module -Xcc -ivfsoverlay -Xcc /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-cgjzvszwmdvqryawymbhwlpsyeok/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/DropDown.build/unextended-module-overlay.yaml -working-directory /Users/markp/projects/RisePrime/Pods Command CompileSwiftSources failed with a nonzero exit code Strange thing that I have been able to remove this error on 3 of my 5 pods that have this error by issuing the command in a terminal. IE the /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc ... command from above error. Unfortunately this does not help me with the last two pods I'm trying to complle (MBPhotoPicker 0.2.3 and IQKeyboardManagerSwift 6.5.9) Also note that this error seems to be dependent on other pods. IE if I remove pods and include a pod that has the error it may disappear. Very frustrating. Have tried all the standard stuff for this error including deintegrating pods, removing DerivedData, clean build, reboot, restart xcode, ...

This cocopod version 0.1.0 depends on Texture 2.3 which depends on Texture/PINRemoteImage 2.3 which depends on PINRemoteImage 3.0.0. But forrums indicat you need to use PINRemoteImage 3.0.3 in Xcode 13/swift 5. Is this cocopod still supported? Anyone using it? Is there a way to override the dependency. One possibility is to try with PINRemoteImage 3.0.3 but I can't figure out how to do that.

I have tried everything so any suggestion would help. I have a project that I received from someone else. I get the following error building on the Bridging-Header.h file :0: error: error opening input file '/Users/wegile/Documents/Richa/Projects/Rise Prime Git/riseprime_iphone_user/RisePrime/RisePrime-Bridging-Header.h' (No such file or directory) :0: error: cannot open file '/Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-dzwiphmacvawjrfzxgbuvupudlar/Build/Intermediates.noindex/PrecompiledHeaders/RisePrime-Bridging-Header-3lvp3nwfcqika.dia' for diagnostics emission (No such file or directory) /Users/markp/Library/Developer/Xcode/DerivedData/RisePrime-dzwiphmacvawjrfzxgbuvupudlar/Build/Intermediates.noindex/PrecompiledHeaders/RisePrime-Bridging-Header-3lvp3nwfcqika.dia:1:1: warning: Could not read serialized diagnostics file: error("Failed to open diagnostics file") (in target 'RisePrime' from project 'RisePrime') Command PrecompileSwiftBridgingHeader failed with a nonzero exit code import-objc-header The build command is using the path of the original developer. /Users/wegile/Documents/Richa/Projects/Rise\ Prime\ Git/riseprime_iphone_user/RisePrime/RisePrime-Bridging-Header.h I have tried everything. Set the path for the Bridging-Header in swift compiler - General -> Objective C Bridging header. See attached Clean build Command-Shift-K Removed DerivedData It seems that this path has come with the configuration files but I don't know how to update to the correct path

I have an old project that has errors with the latest cocopods because it references UI functions that have changed. Where do you configure the project to point to the correct UIKit.

I am new to IOS development. Is this typical that pods are not compatible with the latest language. I'd love to know what designers typically do to handle these compatibility issues. Do you typically run an older verision of Swift to be compatible. with existing PODS? I'm running Xcode version 13.1 and MAC Monterey (12.0.1) I'm working on an application that has been dormant for a while and a lot of the pods have compatibility issues. Including swift 5 warnings and depricated methods. What is the standard practice. Should I be using older versions of xcode and swift to be compatible with existing pods.

I'm new to xcode and IOS app development. I have received a project from someone that I will be working on. When I open in Xcode all I get is a spinning wheel. I have two proejects and the both do the same thing. Any recommendation on where to start? Are there logs I can look at to determine why the project wont load?