After updating from Kotlin 1.8.10 to 1.8.20, I ran...
# kotlin-native
j
After updating from Kotlin 1.8.10 to 1.8.20, I ran into this error. Any idea if there's a workaround?
s
Hey, are you able to create a reproducer project for us?
And thank your for the detailed Report 😍 even without reproducer, we will be looking into it soon!
j
Yes, I'll try to create a simple reproducer for you. Thank you for looking into it!
I attached a reproducer project to the YouTrack issue.
s
Thx. Fixed, will try to get this into 1.8.21
d
Yes! Thank you @Jeff Lockhart for nailing this one down and @Sebastian Sellmair [JB] for the fast response to fix.
I had been desperately trying to create a minimal reproducer of this issue from my own project, but failing - applying the latest dev
1.8.21
KGP does indeed fix it 😌
(This really made my day yesterday!)
@caffeine I believe you also ran into this same problem ☝️
s
(This really made my day yesterday!)
And this really, made my day today 🥹
d
Whoops - sorry to say we may have swapped one problem for another:
Compilation failed: Linking globals named 'knifunptr_cocoapods_<redacted>0_<redacted>VersionNumber_getter': symbol multiply defined!
...my project includes this pod in two modules; if I remove it from either, it's not found, if I include it in both, it's a duplicate at linking.
☝️ Looks like a re-occurrence of this issue
s
Thats unfortunate. However, the issue and the other issue you experience just have the same root cause but are not caused by each other. In 1.8.20 cinterops can have dependencies on each other, there composite builds were freshly introduced by a new mechanism. I very sorry, the second issue you experience is likely to be investigated for 1.9. The only chances for us getting into 1.8.21 with the second issue is if you could provde a reproducer within the next few hours and the fix is very simple
d
Ok, thanks for letting me know @Sebastian Sellmair [JB] 👌
s
1.8.21 is currently in the process of releasing… Sorry folks
If its really blocking you from upgrading, then please tell me, we can figure out what we could do for you.
cc @atyrin: Can you help here? I tried, but could not reproduce the issue in 1.9 master