Hi, I am very frustrated with having my app repeatedly rejected for issues I can't fix because they don't exist.
So I'm trying to publish this app that offers some consumable iAP that is used to unlock a pairing app on a 3rd party platform.
Originally the app did not have an account system, it was rejected by Apple on the grounds that the user may want to restore previously unlocked paired apps. We added a an optional(as the reviewer suggested) sign in with Apple support if the user wants to secure their unlocked installations.
Then we got rejected for forcing account creation, data collection and no ability to delete the account. Forcing account creation is false but maybe the reviewer was confused therefore we put explicit explanation under the sign in with Apple button noting that this is optional, reduced the required profile details to 0 for sign in with Apple and added very simple account deletion UI that is displayed on the same screen where the user sign in with Apple.
And yet we get another rejection about forcing the users to create account to be able to do iAP(factually false) and that we don't have account deletion feature(again factually false).
How to handle that? I have no idea how to fix issues that don't exist. I also run out of space for explaining the reviewer how things work in the app and this is an extremely simple app that does have exactly 2 views, one to scan the devices to connect and one to do playback on those devices and purchase the full version of the app to remove limits on playback.