+
+ |
+ Before |
+ Now |
+
+
+ Dependencies of the jvmMain compilation |
+
-* Consider two objcinterop libraries: one that uses `objcnames.protocols.ForwardDeclaredProtocolProtocol` and another
- that has an actual definition:
+```kotlin
+jvm
+```
- ```ObjC
- // First objcinterop library
- #import
-
- @protocol ForwardDeclaredProtocol;
-
- NSString* consumeProtocol(id s) {
- return [NSString stringWithUTF8String:"Protocol"];
- }
- ```
+ |
+
- ```ObjC
- // Second objcinterop library
- // Header:
- #import
- @protocol ForwardDeclaredProtocol
- @end
- // Implementation:
- @interface ForwardDeclaredProtocolImpl : NSObject
- @end
+```kotlin
+jvmCompilation
+```
- id produceProtocol() {
- return [ForwardDeclaredProtocolImpl new];
- }
- ```
+ |
+
+
+|
- Previously, it was possible to transfer objects between them seamlessly. Now, an explicit `as` cast is required
- for the forward declaration:
+```kotlin
+dependencies {
+ add("jvmImplementation",
+ "foo.bar.baz:1.2.3")
+}
+```
- ```kotlin
- // Kotlin code:
- fun test() {
- consumeProtocol(produceProtocol() as objcnames.protocols.ForwardDeclaredProtocolProtocol)
- }
- ```
+ |
+
- > You can only cast to `objcnames.protocols.ForwardDeclaredProtocolProtocol` from the corresponding real class.
- > Otherwise, you'll get an error.
- >
- {style="note"}
+```kotlin
+dependencies {
+ add("jvmCompilationImplementation",
+ "foo.bar.baz:1.2.3")
+}
+```
-**When do the changes take effect?**
+ |
+
+
+ Dependencies of the jvmMain source set |
+
-Starting with Kotlin 1.9.20, you need to explicitly make a cast to and from the corresponding C and Objective-C forward
-declarations. Also, it's now only possible to import forward declarations by using special packages.
+```kotlin
+jvmMain
+```
-## Incorrect version of iOS framework after Kotlin upgrade
+ |
+
+
+ Dependencies of the jvmTest compilation |
+
-**What's the issue?**
+```kotlin
+jvmTest
+```
-Changes in Kotlin code might not be reflected in the iOS app in Xcode when direct integration
-is used. The direct integration is set up with the `embedAndSignAppleFrameworkForXcode` task, which connects the iOS
-framework from your multiplatform project to the iOS app in Xcode.
+ |
+
-This can happen when you upgrade the Kotlin version from 1.9.2x to 2.0.0 in your multiplatform project (or downgrade it
-from 2.0.0 to 1.9.2x), then make changes in Kotlin files and try building the app, Xcode may incorrectly use the previous
-version of the iOS framework. So, the changes won't be visible in the iOS app in Xcode.
+```kotlin
+jvmTestCompilation
+```
-**What's the workaround?**
+ |
+
+
+ Dependencies of the jvmTest source set |
+
-1. In Xcode, clean build directories using **Product** | **Clean Build Folder**.
-2. In the terminal, run the following command:
+```kotlin
+jvmTest
+```
- ```none
- ./gradlew clean
- ```
+ |
+
+
-3. Build the app again to ensure that the new version of the iOS framework is used.
+The available scopes are `Api`, `Implementation`, `CompileOnly`, and `RuntimeOnly`.
-**When will the issue be fixed?**
+**When do the changes take effect?**
-We're planning to fix this issue in Kotlin 2.0.10. You can check if any preview versions of
-Kotlin 2.0.10 are already available in the [Participate in the Kotlin Early Access Preview](eap.md) section.
+In Kotlin 1.8.0, an error is introduced when using old configuration names in hard-coded strings.
-For more information, see the [corresponding issue in YouTrack](https://youtrack.jetbrains.com/issue/KT-68257).
+For more information, see the [corresponding issue in YouTrack](https://youtrack.jetbrains.com/issue/KT-35916/).