hey iOS folks, just a heads up, if you are on Kotl...
# kotlin-native
n
hey iOS folks, just a heads up, if you are on Kotlin 1.3.61 or below and is about to switch to Xcode 11.4 (Swift 5.2), brace yourselves for impact as this issue’s fix hasn’t made it into the 5.2 release: https://bugs.swift.org/browse/SR-12169.
💥 1
👍 2
the original report (I stress that it’s a Swift bug though, not Kotlin’s): https://youtrack.jetbrains.com/issue/KT-36425 There’s a comment explaining why it’s not an issue in 1.3.70+.
n
@basher good call making sure the attribute is not actually emitted anymore
@basher I checked my 4,5k line K/N framework header and
objc_runtime_name
is nowhere to be found
(anecdotal evidence, I know)
b
🎉 they confirmed fixed too
r
Hopefully a version with the fix appears soon
b
Kotlin 1.3.70 is already out. With WWDC somewhat around the corner, I would not expect a Swift or Xcode update anytime soon
r
Kotlin 1.3.70 (and 71) cause multiple bugs which prevent us from updating so
I’ll have to fetch and install XCode 11.3 as it got auto updated
b
Happy to help more with the CoroutineWorker bug with a GH issue 🙂 (as much repro as you can provide)
r
I need to work on features right now, I spent too much time making everything work for 1.3.61 🙂 But maybe next month. There are other issues than this one too
👍 1
n
meanwhile, Xcode 11.4.1 should fix the bug affecting Kotlin < 1.3.70:
Fixed a crash that could occur in Swift code that imported an Objective-C class defined with the objc_runtime_name attribute. (60888835)
🎉 1
(although the radar number doesn’t match the one in SR-12169 ¯\_(ツ)_/¯)
nah, checked out an old commit (with Kotlin 1.3.61) to verify the fix and nope, still crashing for me. Not sure what fixed there. Sorry for false hope.
r
Anyone tried Kotlin 1.3.61 with XCode 11.5 yet?
n
it’s finally claimed to be fixed in Xcode 12
(i.e. Swift 5.3)
just checked, it is
r
Well let’s wait for the release then