Recently I made a game in Unity Engine. The game is original, from source code to images down to audio. It was successfully accepted in every store from the very first submission -even Apple-. A week later I discovered a bug in the game’s advanced stages and pushed for an update, along with newer artwork for the App presence screenshots. This is when my troubles began. The infamous Guideline 4.3 Design spam took over.
Sep 19, 2019
Apple Reviewer: “This app duplicates the content and function, submitted by you or another developer to the App Store…”
Me: “Hmm, I don’t have any other apps on the store. I researched for a game like mine. I didn’t find anything like it. Mine is quite genuine”. (proof: Trailer)
Apple Reviewer: "Apps that simply duplicate content… "
Me: ( responding with over five paragraphs to the Apple Reviewer, contemplating the insanity for anyone to label my work spam, providing sufficient and succinct evidence of my work quality in both content and context, finishing with an appeal, demanding a logical explanation behind this appears-to-be technical error )
Sep 21, 2019
I receive neither response from the Apple Reviewer nor the Apple Board Team. Realizing this is going to be a long one.
I made a new build, removed some of the beautiful artwork on the App presence and resubmitted (guessing it had something to do with it). Yet once again Apple Guideline 4.3 Design spam is injected into my status.
Apple Reviewer: “Specifically, this app appears to be available in the same territories as another identical app submitted to the App Store. It would be appropriate to restrict the available territories for individual apps to those areas in which you intend to market and sell it and ensure none of the selected territories overlaps.”
Me: ( resubmits the same build with fewer territories for review )
Guideline 4.3 Design rejection did cost many Apple developers frustration, time and agony.
So what could be causing this spam error?
- Are Apple Reviewers bots? Or simply simple humans? If it’s a machine then my guess it’s detecting a spam code from one of Unity’s libraries or Xcode ( likely the IAP is deprecated, in which case I would relay on something like, KLGenerateSpamCode )
- While I am certain I surpassed the Apple Guideline of 2.3 Accurate metadata. It could be the screenshots I recently provided are an artwork of the game ( not actual gameplay Screenshots )
- Could it be Keywords? ( I did make broad ones )
- if you do make a build in Unity for iOS you’ll receive a project labeled Unity-iPhone as in your Xcode project. Could there be a collision between the App Store binary data and the project name
Xcode : 10.2.1
Unity : 2018.4.0f1
Thanks