A question I’m struggling to give a good answer to: I know that Xcode updates often require a Kotli...

# ios

[Ben]

A question I’m struggling to give a good answer to:

I know that Xcode updates often require a Kotlin version bump before a KMP project can be built with the new Xcode. But if we produce an XCFramework from a Kotlin module, what’s the likelihood of that XCFramework not being compatible with an app built with a newer Xcode, until it’s itself built with a compatible version of Kotlin+Xcode?

Basically, if we produce a library that our iOS team consumes, can we reassure them that they won’t risk get blocked on Xcode updates until a new Kotlin version is out?

[Konstantin Tskhovrebov]

You are right. But as I know there is a gold ios dev rule: not update xcode too early because it has a lot of problems after a release

[Landry Norris]

Would this not have the same effect as compiling a Swift library with an older XCode? There should be a period of backwards compatibility.

[Konstantin Tskhovrebov]

There shouldn't be problems, to be honest. Frameworks compiled previous xcode version should work fine with new xcode versions

[Konstantin Tskhovrebov]

There is a problem in another direction: in some cases a framework compiled by newer version xcode couldn't be linked by the previous version of the xcode

[Konstantin Tskhovrebov]

(the case is the using of a new API from a new ios SDK)

[Ben]

Thanks - so is the answer that KMP doesn’t introduce anything which might make this more likely over a plain Obj-C or Swift library?