Account Deletion for Apple Store Reviewers

Question

Created Apr ’22

Replies 4

Boosts 1

Views 2.7k

Participants 3

We recently added the ability for a user to delete their account as per the 5.1.1 guidelines.

Our app was later rejected because the account we provide for logging in was deleted by an Apple reviewer. We can create a new account that reviewers can use to sign in, but how do we prevent this from happening again? I understand the desire to verify account deletion, but if reviewers are constantly deleting the account used for approval, we'll be in an endless cycle of rejections. What should we do?

Answered by lisamartin00 in 711987022

Here's what our team has decided to do in case anyone else runs into this issue:

Recreate an account similar to the one that the Apple Store reviewer deleted (with the correct data, permissions, etc.)
In the delete account code, check for this account and don't allow it to be deleted. Instead, show a modal that explains that this specific account cannot be deleted, and if they would like to test account deletion, they can log out and create a brand new account to delete.
Include this info in the review notes.

This way, the onus is on them to create new accounts if they need them, they can still test account deletion, and the reviewer account will be preserved. Hopefully, they will accept this approach. This definitely doesn't solve anything for apps where you are required to go through some sort of buyflow to even create an account though. I'll be interested to hear what people come up with when June 30 rolls around.

Boost

Answer 1

Claude31 OP

Apr ’22

What is the exact reason given for rejection ?

Do you see on your server that this account was deleted ?

Did you explain in your comments to reviewer how to use the account you provided ?

0

Answer 2

lisamartin00 OP

Apr ’22

Here is the exact reason given for the rejection:

We discovered one or more bugs in your app. Specifically, when attempting to login using the email address provided an error appears on the screen.

Seeing an error on the screen in this case is expected because in a previous review, they deleted the account we provided them with. Now they cannot log in with that account anymore.

Yes, we have already confirmed they have deleted the account.

We did not explain to them not to delete their account, but maybe this is what we need to do to prevent them from testing this part of the app? Since there is not much documentation on how 5.1.1 is supposed to be tested by Apple reviewers, I don't really understand what we're expected to provide them (new credentials every time we submit in case they test to delete?). I'm just not really sure how other developers will be solving this problem. It seems like everyone will be in the same boat as soon as they add this functionality to their app by June 30.

When we asked them what we should do and explained exactly what I explained above in my first post, we received a canned response with links to developer docs and this forum.

0

Answer 3

endecotp OP

Apr ’22

new credentials every time we submit in case they test to delete?

Yes. Or give them a list of 100 accounts and tell them to pick one at random.

Also, make your error message say “You deleted this account on Date at Time” and maybe even “click here to un-delete”, not just “error no such account”.

0

Answer 4

lisamartin00 OP

Apr ’22

Accepted Answer

Here's what our team has decided to do in case anyone else runs into this issue:

Recreate an account similar to the one that the Apple Store reviewer deleted (with the correct data, permissions, etc.)
In the delete account code, check for this account and don't allow it to be deleted. Instead, show a modal that explains that this specific account cannot be deleted, and if they would like to test account deletion, they can log out and create a brand new account to delete.
Include this info in the review notes.

This way, the onus is on them to create new accounts if they need them, they can still test account deletion, and the reviewer account will be preserved. Hopefully, they will accept this approach. This definitely doesn't solve anything for apps where you are required to go through some sort of buyflow to even create an account though. I'll be interested to hear what people come up with when June 30 rolls around.

0