Hello,
I have a question regarding the Mac App Store deployment and App Review process.
Our macOS app will also be distributed on the Steam platform. In our current build setup, the App Store build output (inside Contents/MacOS/) may still contain Steam-related dynamic libraries (e.g., libsteam_api.dylib) and metadata/configuration files (such as .txt files used only by Steam)
These files are not used in the App Store version. Users will not see any Steam-related information, functionality, or UI when the app is running. Their presence is simply a byproduct of the current packaging process.
My concern is whether including such unused Steam-related files in the App Store submission could be considered a violation of App Store Review Guideline 2.3.10, or otherwise lead to rejection during review.
Would Apple recommend that we strictly separate the build targets so that the App Store submission does not contain any Steam-related files, even if they are unused and invisible to the user?
Thank you very much for your guidance.
While I absolutely agree that it makes sense to talk to App Review about this directly, I want to address this point specifically:
the … build output (inside Contents/MacOS/) may still contain Steam-related dynamic libraries … and metadata/configuration files …
Contents/MacOS/ is not the right place for dynamic libraries or configuration files. Placing content in a bundle is very clear about this. It also has this warning:
If you put content in the wrong location, you may encounter hard-to-debug code signing and distribution problems. These problems aren’t always immediately obvious.
IMO you should follow the rules from that document regardless of what distribution channel you’re using.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
