Custom-built VPN app repeatedly rejected under 4.3(a), now 5.6

Question

THANLAR OP

Created 1d

Replies 1

Boosts 0

Participants 2

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.

Answer 1

SoheilManagment OP

1h

Hello. Our team has encountered this issue before Unfortunately, since most of the VPN cores used by other developers have identical binaries, almost identical in terms of code and size Apple's system or your app reviewer may even associate your app with that account To solve this issue, you need to customize the core and fully personalize it and provide the user with a different experience in terms of IP and .... to make the app unique Cores such as v2ray , openvpn ,wireguard and more ... We even received a warning from Apple for this reason, and after that we were very careful that developers who violate the rules and use public code do not get us into trouble, and to the extent possible, customize and personalize public code whose development from scratch is not cost-effective and has no justification and makes no difference, for your own purposes.

Good luck.