Hi,
I’m looking for technical advice on a repeated App Review issue with our app, ASK VPN (Apple ID: 67...).
ASK VPN is a simple consumer VPN app for iOS. It uses Apple’s Network Extension / Packet Tunnel APIs. Users sign in, retrieve their assigned VPN profile, view account status/expiry, and connect through a single main connection flow.
The app was built specifically for this project. We did not purchase or reuse a VPN template or source code from another developer. I designed the product flow and UI, and used Codex AI as a development assistant.
Our rejection history is:
- Guideline 4.3(a): Apple said the app had a similar binary, metadata, and/or concept to apps submitted by other developers, including one associated with a terminated Developer Program account.
- We reviewed the app, changed product-specific functionality and UI, added onboarding, privacy/VPN disclosures, localization, support features, diagnostics, and clarified the implementation to App Review.
- The latest rejection is now Guideline 5.6, stating that the app contains features that appear to have been intentionally hidden during review.
We do not intentionally hide any functionality from App Review, and we have not been told which specific feature or behavior is considered hidden.
One thing that concerns me is that the app often moves to In Review and is rejected very quickly.
My main questions are:
- What technical factors can cause a custom-built VPN app using Network Extension / Packet Tunnel to be associated with another developer’s app or terminated account?
- What kinds of implementation or server-side behavior commonly lead App Review to conclude that functionality is being intentionally hidden?
We are willing to provide Apple with complete source code, backend/API details, test accounts, and configuration if there is a secure review path for that.
I would appreciate advice from anyone who has seen a similar 4.3(a) → 5.6 progression.
Thank you.