Dynamic frameworks are currently necessary to see Kotlin debugging info from iOS. However, dynamic frameworks also require cleaning (CMD+SHIFT+K) and rebuilding to pull in any changes to the Kotlin code, which adds significantly to build times.
If you want to avoid cleaning the iOS project every time you make changes to the Kotlin code, you can still use a static framework, but you will not be able to see useful debugging information.
We're currently working towards a solution to give the best of both worlds.
Dynamic frameworks are currently necessary to see Kotlin debugging info from iOS. However, dynamic frameworks also require cleaning (CMD+SHIFT+K) and rebuilding to pull in any changes to the Kotlin code, which adds significantly to build times.
If you want to avoid cleaning the iOS project every time you make changes to the Kotlin code, you can still use a static framework, but you will not be able to see useful debugging information.
We're currently working towards a solution to give the best of both worlds.