Sure, I tested the production config, and the conditional compilation with #if DEBUG behaved just as expected. Nevertheless, analyzing the archived app with strings did produce LSApplicationWorkspace among other strings.
I suspect this may have to do with Strip Debug Symbols During Copy (COPY_PHASE_STRIP) and/or Generate Debug Symbols (GCC_GENERATE_DEBUGGING_SYMBOLS) build settings which default to NO and YES, respectively, for all configurations. Haven’t tested it yet, though.
XMaster
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
User for
Post
Replies
Boosts
Views
Activity
You’re right in that LSApplicationWorkspace is a pretty powerful class. Among other things, it can launch apps by bundle IDs, which I initially wanted to use for opening Settings’s main screen (the UIApplication.openSettingsURLString constant points to an app’s settings, which wan’t quite suitable for my goal).
I found https://developer.apple.com/documentation/financekitui/addordertowalletbutton and https://developer.apple.com/documentation/financekit, but neither of them has any documentation whatsoever—it’s like they’re not meant to be discovered. Could you confirm I’m looking in the right place?