A viewer app submission is rejected in iTunes Connect with the message, "Invalid Binary." An email from Apple provides further detail, indicating "The following keys cannot have wildcards in their values..."
Currently, Adobe App/Viewer Builder-created apps don't support iCloud, Passes, or Data Protection features of iOS. Enabling them in the iOS Provisioning portal causes the Application Loader, to reject the binary based on missing values expected when those features are enabled. (The Application Loader performs some preflighting before uploading the binary.)
The following is an example of the detailed message explaining the rejection of the viewer app based on iCloud enablement. Passes and Data Protection are expected to be similar:
Invalid Code Signing Entitlements - The signature for your app bundle contains entitlement values that are not supported. For the com.apple.developer.ubiquity-container-identifiers entitlement, the first value in the array must consist of the prefix provided by Apple in the provisioning profile followed by a bundle identifier suffix. The bundle identifier must match the bundle identifier for one of your apps or another app that you are permitted to use as the iCloud container identifier.
Specifically, value "G3Z86DQZ5B.*" for key "com.apple.developer.ubiquity-container-identifiers" in viewer is not supported.
Invalid Code Signing Entitlements - The signature for your app bundle contains entitlement values that are not supported.
Specifically, value "G3Z86DQZ5B.*" for key "com.apple.developer.ubiquity-kvstore-identifier" in viewer is not supported.
Once these issues have been corrected, go to the Version Details page and click Ready to Upload Binary. Continue through the submission process until the app status is Waiting for Upload and then use Application Loader to upload the corrected binary.