App Rejected Due to an Account Restriction, Not a Bug – No Response from Apple After Fixing the Issue

Hello everyone,

I'm an independent developer, and I'm currently stuck in the App Review process. I'm hoping someone who has experienced something similar can offer some advice.

My app was rejected because the reviewer encountered an error message when attempting to make an in-app purchase.

However, this was not a technical bug or a StoreKit issue. It was an intentional account protection rule in my app.

Here's what happened:

My app has a rule that one Apple ID subscription can only be linked to one app account at a time. This prevents other accounts from taking over someone's paid subscription or sharing a single subscription across multiple accounts.

During Apple's review, the sandbox Apple ID used by the reviewer had apparently already been linked to another test account. When the reviewer attempted to purchase a subscription using a different account, the app correctly triggered this restriction.

Apple interpreted this behavior as a purchase failure and rejected the app.

What I've done to resolve it:

Although this rule is intentional and designed to protect users, I wanted to make the review process as easy as possible.

I updated our server to remove this restriction specifically for sandbox subscriptions. Reviewers can now complete purchases and restore subscriptions even if their sandbox Apple ID was previously linked to another test account.

The restriction remains unchanged for real production subscriptions.

On November 17, I explained the situation to the App Review team and informed them that the sandbox issue had already been resolved. I asked them to test the purchase flow again.

On November 18, I also requested a phone call to clarify the situation.

The problem is that nobody has responded.

I have not received any acknowledgment of my explanation, no response to my request for another review, and no phone call.

I have also tried contacting Apple through the appeal process, but I still haven't received a response.

At this point, I don't know what else I can do. The issue encountered during review has already been addressed, and no new app binary is required because the change was made entirely on our server.

Has anyone experienced a similar situation where an app was rejected because an intentional business rule was mistaken for a bug?

How did you get the App Review team to respond after explaining and resolving the issue?

Is there any effective way to escalate this situation when both review messages and appeal requests go unanswered?

submission ID
78b8dd94-fd4c-4951-959b-4fdb57a659d7

I would really appreciate any advice. Thank you!