مسارات CI لـ Android وiOS

KMP shares code but still ships two apps. Good CI builds, tests and packages both Android and iOS automatically on every push.

Your biggest win is shared logic. Run the commonTest suite in CI so a broken rule is caught once, before it reaches either app.

For Android, CI assembles the APK or bundle. The assembleRelease task produces the artifact your release step will later upload.

iOS jobs must run on a macOS runner with Xcode. Linux cannot compile the Kotlin/Native framework or build the iOS app.

Fresh runners are slow. Caching the Gradle home and Kotlin/Native dependencies across jobs avoids redownloading the world each time.

If iOS uses pods, cache the Pods folder. Skipping a full pod install on every run shaves real minutes off the iOS job.

Keep Android and iOS as separate jobs so one failing platform does not hide the other, yet both fire from the same push.

Release builds need keys. Store the keystore and certificates as encrypted secrets, never committed in the repository.

Run lint and formatting checks early. Catching style and obvious bugs up front saves expensive build minutes on doomed runs.

Save the APK and iOS artifact from each run. Testers can grab a build directly instead of waiting for a manual export.

Run the full suite on every pull request and block merges until it is green, so main stays releasable at all times.

You ran shared tests in CI, built both apps with Android on Linux and iOS on macOS, cached dependencies, signed with secrets, and gated merges on green. ✅