App Review Receiving Different Configuration Errors Across Submissions for the Same Build

We are looking for guidance from developers who may have faced similar App Review scenarios.

Our app has been rejected under Guideline 2.1(a) - Performance - App Completeness with the following feedback: "We continue to find a configuration error occurs when we attempt to install the app and demo profiles."

What makes troubleshooting difficult is that we have received different rejection reasons across multiple review submissions for the same build and enrollment flow.

We have been unable to reproduce these issues internally across our test devices.

Has anyone experienced situations where:

  1. Different App Review submissions report different failures for the same build?
  2. Enrollment or configuration profile workflows behave differently on App Review devices than on internal test devices? What could be the contribution factors?
  3. Cached profiles, device state, or repeated profile installations have contributed to inconsistent review results?

We are working with App Review through Resolution Center, but any advice on how to obtain more actionable reproduction details or handle inconsistencies between review attempts would be greatly appreciated.

Thank you.

App Review Receiving Different Configuration Errors Across Submissions for the Same Build
 
 
Q