Hello, I have a few questions about how App Review handles A/B testing and remote configuration, so I can make sure an app is compliant before submission. A/B testing: Is it allowed under Guideline 2.5.19 to A/B test paywall designs, subscription or consumable offers, and some content features with a server-side remote configuration service (e.g. Firebase Remote Config), so that different users see different variants? Review access: If this is allowed, what is the expected way to make all variants available to App Review? Is it enough to describe every variant in the Notes for Review, or should the reviewer also be able to switch between variants in the app? Changes after approval: If a new paywall variant or feature is enabled through remote configuration after a version has been approved, does it need a new submission? Or is it acceptable if it was described in the review notes of the approved version? Review-specific behavior: Is there any case where an app may behave differently for App Review than for regular users, or should the reviewed experience always be identical to what users get? DPLA Section 3.2(f): Could you give examples of what kind of app behavior is considered "interfering with" App Review or "evading the review process" under Section 3.2(f)? Thank you for your help. Best regards