KiteSsotIosSyncExtension

Apple source sync policy inside kiteSsot { ios { rewrite { ... } } }.

Writing this block is the opt-in. Its presence is what authorizes the explicit Apple source tasks, and it replaces the old syncIos = true flag.

kiteSsot {
    ios {
        rewrite {
            targets("iosApp")
            cleanPlist = true
            onConflict = PlistConflictPolicy.KEEP

            renameSharedModule(from = "OldShared", to = "Shared")
        }
    }
}

Authorizing is not running. This block starts nothing. An ordinary build still never touches an Apple source file. You run kiteInternalIosConfig, kiteInternalPlistClean, or kiteInternalIosLogo yourself, and every safety rail still applies: the root dryRun previews instead of writing, the root backups keeps recovery copies, and onConflict decides what happens when an existing plist value disagrees with yours.

Which task this block unlocks

What happens on a plist conflict

See also