KiteConfig/io.github.yuroyami.kiteconfig/KiteDebugScope

KiteDebugScope

What a debug build changes, inside kiteConfig { debug { ... } }.

The debug build is the one Android Studio and Xcode install while you work. Give it its own identifier and it installs next to the released app instead of replacing it. Give it its own name or icon and you can tell the two apart.

kiteConfig {
    appName = "Jetzy"
    appId   = "com.example.jetzy"
    debug {
        appId { suffix = ".debug" }               // com.example.jetzy.debug
        appName = "Jetzy Dev"
        logo { background = color("#B00020") }   // same mark, red plate
    }
    android { debug { appId { suffix = ".dev" } } }   // Android gets com.example.jetzy.dev
}

member	meaning	default
`appName`	the debug build's display name	the platform's release name
`appId`	the debug build's exact identifier	the release id plus `appId { suffix }`
`appId { suffix }`	added to the end of the platform's release identifier	none
`logo { }`	the debug icon; any logo value you leave unset uses the release icon	the release icon

Nothing here is on until you set a value, so an empty block changes nothing. Each value also needs its release value to reach that platform. Each value is looked up closest first: the platform's own debug { }, then this block, then that platform's release value.

Android uses this for its debug build type, iOS for its Debug build configuration. Desktop has no debug build, so desktop { } has no debug { }.