Post

Replies

Boosts

Views

Activity

Terminate
Hello everyone, why should our account with a binary file that is public and all developers can use it be closed according to the 4.3 guideline? But Planet VPN which has more than 11 apps and many other developers can easily use it and there are no problems, be closed? Are these rules only for our company with more than 20+ employees? That our years of effort can end in one day with the decision of an inspector who only checks a system message? Maybe you can check the links: https://apps.apple.com/ae/app/japan-vpn-secure-proxy/id6499425450 https://apps.apple.com/ae/app/vpn-canada-fast-private/id6499426249 https://apps.apple.com/ae/app/vpn-turkey-fast-and-private/id6499426037 https://apps.apple.com/ae/app/vpn-india-private-secure/id6477943653 And you have access to more than 7 other apps and you can see the developer page, blocking an account because of a legal line is not right! According to Apple's fraud or abuse or circumvention rules, this could include account banning, but we can prove with evidence that the reason for marking binary similarity with other developers is simply a public branch that all developers can use on GitHub. Is there really anyone who monitors that the review team does not make dictatorial decisions? If they do not review for more than a month or continue to refuse to accept the developer's application for approval despite explanations and documentation, they have not made a mistake. But if the developers do not change the structure of a public library that is not necessary to build at all due to the similarity of the work, like OpenVPN at its core, they are linking you to other developers who have violated the rules!!! I agree with you, a reviewer whose literacy is at the level of a primary school child. https://github.com/XTLS/Xray-core Many developers may use this core and break the rules. There is no reason why your system should automatically attribute it. You can also impose the same due to the inconvenience and harassment of other developers. You can decide with your own eyes and mind. I wrote this so that maybe a good and responsible person can solve it. Respect to the review team and their senior managers. Regards
0
0
242
2w
Awaiting a reply in Resolution Center — Guideline 4.3(a) on an app we built ourselves
Hello, I apologise for posting here. I know this forum is not a support channel, and I would not have posted if I had another way to reach App Review. Apple ID: 6759336435 Submission ID: 59a73f4a-e83b-4fa4-96dc-4c4b6a0ebcc4 Version reviewed: 1.0 (3) In review since: August 10, 2026 Rejection received: August 20, 2026 Our first submission was rejected under Guideline 4.3(a), on the basis that the app shares a similar binary, metadata or concept with apps previously submitted by a terminated Apple Developer Program account. We have no connection to any terminated developer account. RocketIO is not related to any other app, including the other apps on our own account. It is a separate product that we have been designing and writing for several years, on a different technical foundation: 114,817 lines of Dart across 139 files in Flutter, plus the Swift we wrote for the iOS tunnel host and the Network Extension, 187 tests, and 32 fully translated languages. We believe the binary match is a false positive. RocketIO statically links a publicly available open-source proxy core, as every app in this category does. That core is the largest part of the compiled binary, so any two apps linking the same open-source library will share a large amount of identical compiled code no matter how different their own source is — exactly as apps linking OpenVPN or WireGuard do. We cannot remove it, because it is the reason the app exists. RocketIO is also a bring-your-own-configuration client rather than a VPN service. It ships with an empty server list and does nothing until the user supplies a configuration for infrastructure they already own. We operate no servers, sell no subscriptions and carry no traffic. Among the protocols we have implemented are several that very few clients support on any platform, including DNSTT (DNS tunnelling), AnyTLS, ShadowQUIC, Mieru and Juicity, some of them added only recently. We replied in Resolution Center with all of this in detail, and asked which app or account the similarity was matched against, so that we could respond to the specific finding rather than guess. We are still waiting for a response. We have deliberately not resubmitted. We did not want to place another submission in the queue while this conversation is open, and we did not want to send back something that could reasonably be read as unchanged. We have been waiting since August 10, and we will be honest that it has been a difficult wait. We put years of work into this app and we have users who are looking forward to it, and at the moment we cannot tell them anything, because we do not know what specifically we are being asked to change. Could someone from App Review please reply to us there? We are glad to provide our source repository and its full commit history, to take a call at any time convenient to you in English, and to demonstrate the app live. Thank you for your time.
2
0
957
3w
Awaiting a reply in Resolution Center — corrected build attached but deliberately not submitted
Hello, I apologise for posting here. I know this forum is not a support channel, and I would not have posted if I had another way to reach App Review. Apple ID: 6799505220 Submission ID: 0a07b03d-56c9-45b4-b9b2-7ecbeb9ada0e Our submission was rejected under Guideline 4.3(a). We investigated and found the cause on our side: a server-side configuration fault meant the reviewed build was served the shared server pool used by our other apps, so it displayed a worldwide server list it was never designed to show. The finding was correct for that build. It was a defect, not the product. We have corrected it and verified the correction, and the corrected build is uploaded and attached to the version in App Store Connect. We have deliberately not pressed Submit for Review. We did not want to place another submission in the queue and take review time from other developers while this conversation is still open, and we did not want to send back something that could reasonably be read as unchanged. We would rather agree the right next step with App Review first. We replied in Resolution Center with all of this and are still waiting for a response. Could someone from App Review please reply to us there? Thank you for your time.
1
0
610
3w
Problem Agreements
Hi everyone, I’m sharing this because I’ve been stuck with this issue for over two weeks, and I still haven’t found a solution — or received a meaningful response from Apple Support. A yellow banner has appeared on my account saying: “The Apple Developer Program License Agreement has been updated and needs to be reviewed.” But here’s the problem: I’ve already accepted the latest agreement long ago. When I log into both: App Store Connect Developer Portal …there’s no new agreement to accept, no prompt, no button — absolutely nothing new. The yellow banner simply refuses to go away, and it's preventing updates. I’ve already: Cleared cache & cookies Tried Safari, Chrome, Firefox Logged in from different devices/networks Verified that I am the Account Holder Reported the issue via Apple Developer Support (more than a week ago) Despite clearly stating the urgency of the matter, I’ve received no fix and no timeline. This is beginning to feel like developers’ time — especially for those who depend on timely releases — isn’t being taken seriously. So I’m writing here to ask: 🔹 Has anyone else encountered this same issue recently? 🔹 Is there any known workaround or fix? I’d appreciate any help or shared experience. Thank you.
0
0
466
Jul ’25
Terminate
Hello everyone, why should our account with a binary file that is public and all developers can use it be closed according to the 4.3 guideline? But Planet VPN which has more than 11 apps and many other developers can easily use it and there are no problems, be closed? Are these rules only for our company with more than 20+ employees? That our years of effort can end in one day with the decision of an inspector who only checks a system message? Maybe you can check the links: https://apps.apple.com/ae/app/japan-vpn-secure-proxy/id6499425450 https://apps.apple.com/ae/app/vpn-canada-fast-private/id6499426249 https://apps.apple.com/ae/app/vpn-turkey-fast-and-private/id6499426037 https://apps.apple.com/ae/app/vpn-india-private-secure/id6477943653 And you have access to more than 7 other apps and you can see the developer page, blocking an account because of a legal line is not right! According to Apple's fraud or abuse or circumvention rules, this could include account banning, but we can prove with evidence that the reason for marking binary similarity with other developers is simply a public branch that all developers can use on GitHub. Is there really anyone who monitors that the review team does not make dictatorial decisions? If they do not review for more than a month or continue to refuse to accept the developer's application for approval despite explanations and documentation, they have not made a mistake. But if the developers do not change the structure of a public library that is not necessary to build at all due to the similarity of the work, like OpenVPN at its core, they are linking you to other developers who have violated the rules!!! I agree with you, a reviewer whose literacy is at the level of a primary school child. https://github.com/XTLS/Xray-core Many developers may use this core and break the rules. There is no reason why your system should automatically attribute it. You can also impose the same due to the inconvenience and harassment of other developers. You can decide with your own eyes and mind. I wrote this so that maybe a good and responsible person can solve it. Respect to the review team and their senior managers. Regards
Replies
0
Boosts
0
Views
242
Activity
2w
Awaiting a reply in Resolution Center — Guideline 4.3(a) on an app we built ourselves
Hello, I apologise for posting here. I know this forum is not a support channel, and I would not have posted if I had another way to reach App Review. Apple ID: 6759336435 Submission ID: 59a73f4a-e83b-4fa4-96dc-4c4b6a0ebcc4 Version reviewed: 1.0 (3) In review since: August 10, 2026 Rejection received: August 20, 2026 Our first submission was rejected under Guideline 4.3(a), on the basis that the app shares a similar binary, metadata or concept with apps previously submitted by a terminated Apple Developer Program account. We have no connection to any terminated developer account. RocketIO is not related to any other app, including the other apps on our own account. It is a separate product that we have been designing and writing for several years, on a different technical foundation: 114,817 lines of Dart across 139 files in Flutter, plus the Swift we wrote for the iOS tunnel host and the Network Extension, 187 tests, and 32 fully translated languages. We believe the binary match is a false positive. RocketIO statically links a publicly available open-source proxy core, as every app in this category does. That core is the largest part of the compiled binary, so any two apps linking the same open-source library will share a large amount of identical compiled code no matter how different their own source is — exactly as apps linking OpenVPN or WireGuard do. We cannot remove it, because it is the reason the app exists. RocketIO is also a bring-your-own-configuration client rather than a VPN service. It ships with an empty server list and does nothing until the user supplies a configuration for infrastructure they already own. We operate no servers, sell no subscriptions and carry no traffic. Among the protocols we have implemented are several that very few clients support on any platform, including DNSTT (DNS tunnelling), AnyTLS, ShadowQUIC, Mieru and Juicity, some of them added only recently. We replied in Resolution Center with all of this in detail, and asked which app or account the similarity was matched against, so that we could respond to the specific finding rather than guess. We are still waiting for a response. We have deliberately not resubmitted. We did not want to place another submission in the queue while this conversation is open, and we did not want to send back something that could reasonably be read as unchanged. We have been waiting since August 10, and we will be honest that it has been a difficult wait. We put years of work into this app and we have users who are looking forward to it, and at the moment we cannot tell them anything, because we do not know what specifically we are being asked to change. Could someone from App Review please reply to us there? We are glad to provide our source repository and its full commit history, to take a call at any time convenient to you in English, and to demonstrate the app live. Thank you for your time.
Replies
2
Boosts
0
Views
957
Activity
3w
Thank you apple
Bye for ever! we go to market android !
Replies
0
Boosts
0
Views
201
Activity
3w
Awaiting a reply in Resolution Center — corrected build attached but deliberately not submitted
Hello, I apologise for posting here. I know this forum is not a support channel, and I would not have posted if I had another way to reach App Review. Apple ID: 6799505220 Submission ID: 0a07b03d-56c9-45b4-b9b2-7ecbeb9ada0e Our submission was rejected under Guideline 4.3(a). We investigated and found the cause on our side: a server-side configuration fault meant the reviewed build was served the shared server pool used by our other apps, so it displayed a worldwide server list it was never designed to show. The finding was correct for that build. It was a defect, not the product. We have corrected it and verified the correction, and the corrected build is uploaded and attached to the version in App Store Connect. We have deliberately not pressed Submit for Review. We did not want to place another submission in the queue and take review time from other developers while this conversation is still open, and we did not want to send back something that could reasonably be read as unchanged. We would rather agree the right next step with App Review first. We replied in Resolution Center with all of this and are still waiting for a response. Could someone from App Review please reply to us there? Thank you for your time.
Replies
1
Boosts
0
Views
610
Activity
3w
App review
Dear Review Team and fellow developers Our app has not been reviewed for more than 7 days despite requesting an expedite Is this normal? Has this happened to us too? I would like to ask the review team to help us with this. Best regards
Replies
2
Boosts
0
Views
235
Activity
Aug ’26
Problem Agreements
Hi everyone, I’m sharing this because I’ve been stuck with this issue for over two weeks, and I still haven’t found a solution — or received a meaningful response from Apple Support. A yellow banner has appeared on my account saying: “The Apple Developer Program License Agreement has been updated and needs to be reviewed.” But here’s the problem: I’ve already accepted the latest agreement long ago. When I log into both: App Store Connect Developer Portal …there’s no new agreement to accept, no prompt, no button — absolutely nothing new. The yellow banner simply refuses to go away, and it's preventing updates. I’ve already: Cleared cache & cookies Tried Safari, Chrome, Firefox Logged in from different devices/networks Verified that I am the Account Holder Reported the issue via Apple Developer Support (more than a week ago) Despite clearly stating the urgency of the matter, I’ve received no fix and no timeline. This is beginning to feel like developers’ time — especially for those who depend on timely releases — isn’t being taken seriously. So I’m writing here to ask: 🔹 Has anyone else encountered this same issue recently? 🔹 Is there any known workaround or fix? I’d appreciate any help or shared experience. Thank you.
Replies
0
Boosts
0
Views
466
Activity
Jul ’25