Collision Issue with existing Kingfisher library

Not sure if I’m alone here but I recently dropped in the UIKit library only to receive conflict (ambiguous / namespace) errors because my app was already using Kingfisher (CometChatPro UIKit provides Kingfisher wrapped) to handle images. The UIKit library uses a public var of “kf” in its extension files but so does the Kingfisher library (again UIKit provides Kingfisher wrapped). The only way I’ve found around this would be to modify the extension file for the UIKit (and all related files) to another variable name which I don’t like due to future updates possibly wiping out the changes. Namespacing with class in my code (CometChatPro.kf etc…) doesn’t work either.

1 Like

Hello @sid,

We have already replaced the Kingfisher library with the name CometFisher so that it won’t conflict with the kingfisher library that exists in your project.
We are also replacing the variable names used in the library in our next release so that after updating the library you’ll won’t face this issue again.

3 Likes

That’s great to hear. I look forward to the release. Thanks @pushpsen.airekar!

1 Like

Hello @sid,

We have released UI Kit - v1.0.1-beta with below improvements.

Added:

  • Forward Message, Share Message.
  • Date headers.
  • Copy - Paste: Single & Multiple Messages.

Replaced:

  • Toast with Snackbar.
  • CometFisher with CometChatKingfisher.

Other:

  • Minor performance improvements.

Kindly, visit the below github repositories for the same.
UI Kit: https://github.com/cometchat-pro/ios-chat-ui-kit
UI Kit Sample App: https://github.com/cometchat-pro-samples/ios-chat-ui-kit-app

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.