I'm trying to understand how the cocoapods plugin works to work around this issue <https://youtrack....

# ios

[ribesg]

I'm trying to understand how the cocoapods plugin works to work around this issue https://youtrack.jetbrains.com/issue/KT-53127/Breaking-change-in-Cocoapods-plugin-between-Kotlin-1621-and-170
Does anyone know why it tries to build a project with the latest versions of the dependencies you specify instead of the right version?
I have this in my Gradle build file:

pod("MaterialComponents/TextFields", "~> 123")

The generated Podfile in build/cocoapods/synthetic/IOS contains this:

pod 'MaterialComponents/TextFields'

Then obviously the Podfile.lock contains:

- MaterialComponents/TextFields (124.2.0)

And the build fails, potentially because this version is broken. Is it a bug? I tried with Kotlin 1.6 and 1.7 and it does not seem different