Questions

Hello Median Support,

I need your help with an Apple App Store rejection for my Afropass iOS app.

The app was created using Median.co from my website:

https://afropass.net

Apple rejected Version 1.0 under Guideline 5.6 – Developer Code of Conduct.

Apple’s exact message was:

“We’ve identified a pattern of unusual behavior with the app that is commonly associated with fraudulent activity. Specifically, the app contains features that appear to have been intentionally hidden during the review process.

Manipulative and misleading behavior is not consistent with guideline 5.6.”

I have NOT intentionally created any Apple reviewer-specific functionality or attempted to hide features from App Review.

Because the iOS application was generated through Median.co, I would like Median to investigate whether anything in the generated project, WebView configuration, JavaScript bridge, app configuration, remote configuration, or other Median functionality could cause Apple to believe that functionality is being hidden during review.

Please specifically investigate the following:

1. Reviewer-specific behaviour
   • Does the Median-generated app contain any logic that detects App Review, Apple reviewers, review accounts, IP addresses, devices, or locations?
   • Is there any functionality that can behave differently for Apple reviewers?
2. WebView behaviour
   • Does the generated application load afropass.net in a way that could cause different content or functionality to be displayed during App Review?
   • Are there any Median WebView rules, injected JavaScript, redirects, user-agent detection, or URL handling that could affect what Apple sees?
3. Remote functionality
   • Can the Afropass website remotely change what is displayed inside the iOS application?
   • Could remote configuration, JavaScript, feature flags, or website changes make certain functionality appear only after App Store approval?
4. Median configuration
   • Please review all Median-generated settings/configuration for this project.
   • Identify anything that Apple could interpret as hidden functionality or manipulation of the review process.
5. Production consistency
   Please confirm that the iOS application submitted to Apple is showing the same genuine production Afropass website and functionality available to normal users.
6. Apple Guideline 5.6
   Please advise specifically what changes Median recommends to make the generated project compliant with Apple’s Guideline 5.6.
7. Generated project
   If there is any Median-generated code or configuration that could have contributed to this rejection, please identify the exact file/setting and provide the recommended fix.

I do NOT want a workaround that simply hides or disables features for Apple.

I want the application to provide the same genuine production experience to Apple reviewers and normal users.

Please also let me know whether you recommend generating a new iOS build from Median after making the necessary changes.

For reference:

App: Afropass
Website: afropass.net
App Version: 1.0
Submission date: 19 September 2026
Apple Guideline: 5.6 – Developer Code of Conduct

Thank you. I would appreciate a detailed technical review because this rejection specifically mentions features being intentionally hidden during App Review.