Closed eviltofu closed 2 years ago
@oa-s @hboon It appears that a library is being embedded twice?
I think it's included as both a pod by us directly and as Swift Package by another Swift Package (WalletConnect v2 SDK)
Since SPM seems to work for us now, try replacing our CryptoSwift dependency in the Podfile
and into SPM? Remember to try to build for both simulator and device?
Maybe it's easier just to remove the SPM version? @hboon
@eviltofu We can't remove the SPM version because the WalletConnect v2 SDK specifies it.
Oh, maybe we can't remove the pod version for the same reason?
Any ideas? Otherwise, let's keep them both around and make sure the version number always sync (not the best idea of course!)
Ok I've checked the entire Podfiles list and it seems like only a handful are not supported on SwiftPackageManager. Blockie, Charts, StatefulViewController, QRCodeReaderViewController, PaperTrailLumberjack, and one or two more.
Maybe shift everything to SwiftPackageManager?
@hboon
Yes, originally wanted to. But like you said not everything third party dependency we use supports SPM. and it looks like SPM can't have dependencies on pods, so we are going to have a mixture anyway. So it doesn't seem like the right time to move completely (or as much as we can) to SPM.
But are you suggesting we move only those pods that depend on CryptoSwift over to SPM? If that's the case, isn't it possible that we might in the future add a dependency that is only available on Cocoapods and we are back to the same problem?
Why not move WalletConnect to the pod file?
Because it's a third party library that only supports SPM. One way to go about it is to create PR to add support for Cocoapods.
So this issue cannot be resolved right now. I'm going to close it if there's nothing else. @hboon
Ok. Let’s close it for now. Maybe we can see if we can add support to the WC SDK for cocoa pods later.