فتح تطبيق iOS وتشغيله في Xcode

Android worked, so let's light up iOS. The iOS app lives in its own folder and you build it with Xcode, not Android Studio. 🍎

Inside the iosApp folder you'll find a project or workspace file. Double-click it to open the iOS app in Xcode.

If your setup uses CocoaPods, always open the .xcworkspace file. The plain .xcodeproj will miss the pod dependencies.

At the top of Xcode, choose the iosApp scheme and a simulator like iPhone 15 from the device dropdown.

The iOS app does not consume Kotlin source directly. It links a precompiled framework that Gradle produces from your shared module.

A custom build phase in Xcode calls Gradle first. That step compiles the shared framework before Swift code is even touched.

Click the Run triangle. Xcode triggers Gradle, builds the framework, compiles Swift, and boots the simulator with your app.

Your Swift screen imports the framework and calls the shared API by name. The same logic that ran on Android now runs on iOS.

The very first iOS build compiles the whole framework, so be patient. Later runs reuse cached output and feel much faster. ⏳

When something fails, open the Issue Navigator. Gradle errors and Swift errors both surface here with a jump-to-line link.

Seeing your shared greeting in the iOS simulator closes the loop. One Kotlin codebase is now powering both native apps.

Let's confirm how iOS consumes your shared Kotlin.

You opened the iosApp in Xcode, picked a simulator, and pressed Run. A build phase ran Gradle to make the framework, then Swift called your shared code live. 🎉