search

crisp-im / crisp-sdk-ios

:package: Crisp iOS SDK, add a chat in any iOS app and communicate with your users.
https://docs.crisp.chat/guides/chatbox-sdks/ios-sdk/
Other
45 stars 19 forks source link

Conflict between Crisp SDK and Stasel's WebRTC Package on iOS #103

Open stormphlegyas opened 1 month ago

stormphlegyas commented 1 month ago

I’m currently developing an iOS application and have encountered a conflict when trying to integrate the Crisp SDK alongside a WebRTC package compiled by the GitHub user Stasel, which is a build of the official Google WebRTC specifically for iOS.

Issue:
The Crisp SDK appears to use a package named “webrtc” that conflicts with the WebRTC package compiled by Stasel : https://github.com/stasel/WebRTC.git). Although I am not using the CrispWebRTC package, the conflict arises due to the Crisp SDK’s inclusion of a binary target also named "WebRTC." This naming overlap prevents both packages from coexisting in my app when imported via Swift Package Manager.

Steps to Reproduce:

  1. Import Stasel's WebRTC package (https://github.com/stasel/WebRTC.git) into an iOS project.
  2. Import the Crisp SDK via Swift Package Manager.
  3. Attempt to build the project.

Expected Behavior:
The project should build successfully with both Stasel's WebRTC package and the Crisp SDK integrated.

Actual Behavior:
A conflict error occurs due to both packages containing a "WebRTC" dependency with the same name, despite not using CrispWebRTC.

Request:
Would it be possible for Crisp to rename their WebRTC binary or otherwise adjust the package structure to avoid this naming conflict? This would greatly assist developers who need both the Crisp SDK and an external WebRTC package in their projects.

Thank you for any guidance you can provide on this issue!