How are people using the new Kotlin debugging with SPM builds?

[lawmaestro]

I've been taking a look at the new Kotlin debugging features in KMMBridge 1.2.0, described here. The prospect of being able to debug SPM builds locally without the need to jump through hoops like locally compiling and changing path mappings sounds great!

However, the part I'm struggling with slightly from the above docs is this:

Third, if you are using KMMBridge to publish SPM, you need to make sure you are creating DEBUG builds. KMMBridge defaults to RELEASE builds. You will need to update your CI flow to enable DEBUG for dev builds and RELEASE for release builds.

I understand what this is saying and how to produce the required debug vs release builds for this feature to work. But what I don't quite follow is how can you deploy a versioned library which uses a release build for an App Store build and a debug build for a Development build? The GitHub workflow deploys either a debug OR release build against a given version. So you can only have one or the other - but surely the most common use-case here would be to need two? Short of having the two build artefacts versioned differently and then dynamically changing the SPM dependency path at build time (based on whether you're building a development or Store build), I'm not understanding how this could be supported.

Has anyone explored this new feature yet and if so, how are you leveraging the new debug support whilst not having debug builds of your KMM library going into App Store releases?