POD Compatibility

From Swift 5, pods should be compatible with newer versions of API (forward compatibility).

API deprecation is another issue, because that's not the API that changes, it's the OS that does not support it anymore. So using old Xcode may not work (and anyway, you will not be able to submit to Appstore).

So if pods are yours, you will have to update for those deprecations.

Could you show some examples of Swift5 warnings and of deprecation ?

Now I'm not sure if this is anything to do with Swift version 5. I created a project that just has pods added. I tried adding SwiftLuhn and got the attached warnings.

Steps to reproduce

1. Updated to Monteray OS version
2. Installed latest xcode (version 12)
3. created new project
4. pod init
5. Added pod 'SwiftLuhn' to podfile
6. Pod Update
7. compile and run

I have added a number of other cocopods and got numerous compile warnings. Some errors also that I'm trying to figure out. My assumption was that the pods would work with the latest versions of OS and Xcode. So just trying to figure out what to do. Since the original post I have found that I can suppress the warnings on the cocopods by using :inhibit-warnings => true but not sure thats the smartest thing to do. Would prefer the pods run clean of warnings.

The pod I'm trying to figure out now is MMChatFramework. It loads the Pod Texture as a dependency which results in the error: "Framwork not found AsyncDisplayKit"

Whether or not they are using pods, apps and libraries may need fixes when new versions of iOS/iOS SDK are released.

Unfortunately, many of the pods are very late about this sort of fixes. (Or old ones might be frozen.)

If updating the versions of the pods to the latest does not solve your issue, you may need to contact to the author of the pods.

moved to comment