Kite
The hands-off switchboard, inside kiteSsot { propagate { ... } }.
kiteSsot {
version = "1.4.0"
propagate {
version = false // this repo edits versionName by hand
}
}Every flag here answers one question: may KiteSSOT apply a value it already knows? Turn one off and KiteSSOT goes quiet. Your Android and Apple DSLs keep exactly what they already say. Nothing is removed, cleared, or rewritten.
The value does not disappear when a flag is off. kiteSsotDoctor still resolves it and prints it, so you can see what would have been applied. These are not safety switches either: no ordinary build mutates source, with or without them.
What each switch stops
| Off | Android keeps | Apple keeps |
|---|---|---|
| appName | its manifest appName placeholder | its PRODUCT_NAME and bundle name keys |
| bundleId | its applicationId | its PRODUCT_BUNDLE_IDENTIFIER |
| version | its versionName and versionCode | its MARKETING_VERSION and CURRENT_PROJECT_VERSION |
| locales | its resource configuration | its knownRegions |
These govern propagation, not mutation. Apple values are written only by an explicit sync task in the first place, so turning one off narrows what that task would write; it does not decide whether it runs.
See also
to preview writes instead of performing them.
for the gate that authorizes Apple writes at all.