You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like SPM is not great in resolving conflicts when there are two same name packages. I already have swift-sdk from another repo and then when I am trying to add Iterable dependencies using the SPM, its colliding with the existing sdk and its not detecting the Iterable sdk at all.
To proof my theory, I did remove the previous sdk from SPM and try to add Iterable and it worked perfectly fine.
The text was updated successfully, but these errors were encountered:
Thanks for suggesting the idea of forking as a wrapper 👍🏼 However, will also see how much effort it is to rename package entirely as a long term solution.
Thanks again
Looks like SPM is not great in resolving conflicts when there are two same name packages. I already have
swift-sdk
from another repo and then when I am trying to addIterable
dependencies using the SPM, its colliding with the existing sdk and its not detecting the Iterable sdk at all.To proof my theory, I did remove the previous sdk from SPM and try to add
Iterable
and it worked perfectly fine.The text was updated successfully, but these errors were encountered: