Pod version resolution issue when both Podfile and pod depend on different versions of same dependency about core

[sharplet]

I've seen the same behaviour. Unfortunately I can't provide any more detail to the reproduction steps here, however I just want to note that in my case the issue is resolved by running pod update. That is, 1) I run pod install, 2) I compile and notice linker errors (duplicate symbols), and 3) I run pod update which removes the duplicate activated pod version.

[phatblat]

I also was able to work around this issue with a 'pod update' and the loose ~> 2.0 pod dependency in my Podfile. This is why this issue was so hard to grasp.

I ran 'pod install' because I had added a new, unrelated pod to the Podfile and got two versions of AFNetworking installed and the compiler errors. In chasing down the errors I ran 'pod update', which ignored the Podfile.lock and upgraded to AFNetworking to 2.2.0 since my original Podfile specified a loose 2.0 dependency. Then no errors.

I wasn't satisfied with simply working around these errors and hence created this issue.

[fabiopelosin]

This issue should be moved to CocoaPods, @phatblat can you do it?

[fabiopelosin]

Moved to CocoaPods/CocoaPods#2002

[phatblat]

Thanks @irrationalfab.

[fabiopelosin]

🍻

[Varsha-Kulkarni]

I'm facing these issues yet!
Analyzing dependencies
[!] Unable to satisfy the following requirements:

• AFNetworking (= 1.3.4) required by Podfile.lock
• AFNetworking (~> 1.3.0) required by RestKit/Network (0.20.3)
• AFNetworking (~> 2.5) required by ABMSoundCloudAPI (0.1.0)

[orta]

@VarshaSameer those dependencies cannot be resolved at all, as you cannot have two versions of the same library in the same codebase.

[Varsha-Kulkarni]

So what would be the solution suggested? Can we actually fork those repos and then change the dependencies within the podfiles?

[orta]

You can do that, but they have different APIs, and RestKit is eventually planning on removing AFNetworking which would fix that. For now, you should fork ABMSoundCloudAPI and make it work with AFNetworking 1.x. Probably way easier than the other way around.

[rijieli]

I am facing the following issue:

I do not want to upgrade the library version for the iOS project, but for visionOS, this library needs to be upgraded to the newest version.