Thank you :) Right now: - I'm building "for developing". Three months later: - "for communicating with End-User-Apps-developers of ... of "various backgrounds" The situation: I see "non-logical logs" of USB-gadget-attachment in "Console.app"; though that app is obviously buggy and "really misses messages", timing of certain "logs' in my tests look "non-logical" (so I am suspecting/expecting huge bugs in the core of OS development) such bugs aren't fatal; but those shall be "stable bugs~=features" but to treat (potential) system-bugs (or my bugs andOS quirks) as "features" I would prefer to have the same (as much as possible) "binaries with resources" at "development" and at "distribution"

It 100% doesn't work in any straight forward manner: "At the project level, you can create different configurations, e.g. Debug (iPad) and Debug (macOS), use .xcconfig files to change the few things that may need to change between macOS and iPadOS, for example the bundle ID of the driver." Debug/Release can't be a matter in this topic. Signing seemingly has no relation to configs. Signing depends on "toolchain". In available XCode15, using (recommended) "automatic code signing", switch between "Apple-developer" (when I build for iPAD) and "Ad-hoc-code signing" (when I build for MAC) works only in IDE. In the dictionary of XCode-15-IDE, for development-convenience I would like to have an opportunity ~automatically assign -"Ad-Hoc-signing" when target is "macOS" ~ "Apple-development" when target is "anything else"