Support
You are writing to a person, not a bot. I answer within two business days, in English, Polish or German.
Something is broken
- describe what you did in the app and what happened next
- add your macOS version and the StorePreflight version
- add the check ID if the problem is about one result, for example
CFG-001 - say whether it happens every time
Please do not attach a full report, a connection log or screenshots of a private project. A full report can contain file names and your notes. The diagnostic export keeps only known check identifiers and statuses, so it is the safe thing to send.
App Store Connect will not connect
Open the connection window, expand the connection log and copy it. It
shows whether the app stopped at the Keychain, at Apple's tool, at the
local module or at the API request. On HTTP 401, check that the
.p8 file matches the Key ID, paste the Issuer ID again
exactly as App Store Connect shows it, confirm the key is still active,
and make sure your Mac sets its clock automatically.
The log never contains keys, tokens, identifiers, app names or paths, so it is safe to send as it is.
A result looks wrong
The scanner reports what it can prove from a file. A signal found in code asks you for a manual review instead of deciding, and a missing artifact is reported as unknown rather than as a violation. If you think a check reads your project incorrectly, describe the case - a minimal fictional example helps most.
Ideas and missing checks
Requests for new checks are welcome, especially with the Apple requirement you have in mind and the artifact that could prove it.
Data handling is described in the privacy policy. The rules of use are in the terms.