KiteConfigBuildConfigExtension

Generated Kotlin constants for your shared code, inside kiteConfig { buildConfig { ... } }.

kiteConfig {
    appName = "Jetzy"
    version = "1.4.0"
    id = "com.example.jetzy"
    modules { shared = ":shared" }

    buildConfig {
        packageName = "com.example.jetzy.generated"

        stringField("BASE_URL", "https://api.acme.com")
        intField("API_TIMEOUT_MS", 30_000)
        booleanField("ANALYTICS_ENABLED", true)
    }
}

Opening this block turns generation on. KiteConfig writes one Kotlin object into the shared project's commonMain, so every platform reads the same constants without an expect and actual pair.

App identity rides along by default: app name, version, version code, Android application ID, iOS bundle ID, and locales. See includeIdentity to turn that off. Android SDK and toolchain values are never included; declare a custom field when runtime code needs one.

The generated file lives in a plugin-owned build directory and never enters your hand-written source tree. Package, object, and field names must be valid Kotlin names.

This is not a secret store. Only public client configuration belongs here. A provider can keep a value out of the build script and out of version control, but the resolved value still reaches generated source and Gradle task inputs. It can also surface in build scans, KLIBs, APKs, IPAs, decompiled binaries, and a trusted build cache when allowBuildCache is on. Never add passwords, private API keys, signing material, or other credentials.

Field helpers

Only stringField accepts a Provider. Give it a fallback: an absent provider fails the build naming the field, rather than emptying the whole set.

stringField("CHANNEL", providers.gradleProperty("channel").orElse("stable"))

What generation requires

See also