Post

Replies

Boosts

Views

Activity

Reply to Own app flagged as 4.1(a) Copycat + "Extended Review" — previous version approved with identical metadata
A 4.1(a) finding on your own brand usually means the reviewer can't connect the App Store account to the "Erendor Online" name. Play Console screenshots don't prove that to Apple, because Google accounts aren't something they can verify. What tends to work: Proof Apple can check: a trademark registration or filing in the account holder's name, and/or an official website on a domain you control. The site should name the developer exactly as it appears on the App Store and link to both store listings. Upload that proof as an attachment in your App Store Connect reply (and in the App Review Board appeal), not only as text. Keep the message short: who you are, the proof, and one line confirming no other developer is involved. Since the metadata didn't change, look at what's new inside 1.1.27 compared with 1.1.24: new art or logos, a link to a fan wiki or Discord, server or community names. One of those is often what the reviewer matched against "third-party content". On the Extended Review flag: there's no way to request its removal directly. It usually drops off after a clean approval, so it's worth getting the ownership proof right before the next resubmission rather than resubmitting repeatedly.
1w
Reply to App stuck after 3.1.1 rejection, replied 8 days ago with no response
Hi Maryyam, you're on solid ground. Guideline 3.1.3(e) (Goods and Services Outside of the App) says that when people pay for physical goods or services used outside the app, you must use a payment method other than In-App Purchase. Yard work and moving help fall under that rule. Reviewers usually flag this because of the word "credits": prepaid credits look like an in-app currency, which falls under 3.1.1. What usually clears it: Stop selling credit packs. Charge per task ("Pay $40 for this job") and tie each payment to a specific booking. In the app, the listing and the screenshots, swap "credits" for "booking payment" or "task payment". In your App Store Connect reply, quote 3.1.3(e) word for word. Add a 3-step path the reviewer can follow (post a task, accept a helper, pay for that task) and state that nothing digital is unlocked. If a stored balance is still needed (for example for refunds), make it refund-to-card only, with no other use in the app. The appeal and your reply run separately. Once you change the build or the wording, resubmit rather than waiting on the appeal.
1w
Reply to Own app flagged as 4.1(a) Copycat + "Extended Review" — previous version approved with identical metadata
A 4.1(a) finding on your own brand usually means the reviewer can't connect the App Store account to the "Erendor Online" name. Play Console screenshots don't prove that to Apple, because Google accounts aren't something they can verify. What tends to work: Proof Apple can check: a trademark registration or filing in the account holder's name, and/or an official website on a domain you control. The site should name the developer exactly as it appears on the App Store and link to both store listings. Upload that proof as an attachment in your App Store Connect reply (and in the App Review Board appeal), not only as text. Keep the message short: who you are, the proof, and one line confirming no other developer is involved. Since the metadata didn't change, look at what's new inside 1.1.27 compared with 1.1.24: new art or logos, a link to a fan wiki or Discord, server or community names. One of those is often what the reviewer matched against "third-party content". On the Extended Review flag: there's no way to request its removal directly. It usually drops off after a clean approval, so it's worth getting the ownership proof right before the next resubmission rather than resubmitting repeatedly.
Replies
Boosts
Views
Activity
1w
Reply to App stuck after 3.1.1 rejection, replied 8 days ago with no response
Hi Maryyam, you're on solid ground. Guideline 3.1.3(e) (Goods and Services Outside of the App) says that when people pay for physical goods or services used outside the app, you must use a payment method other than In-App Purchase. Yard work and moving help fall under that rule. Reviewers usually flag this because of the word "credits": prepaid credits look like an in-app currency, which falls under 3.1.1. What usually clears it: Stop selling credit packs. Charge per task ("Pay $40 for this job") and tie each payment to a specific booking. In the app, the listing and the screenshots, swap "credits" for "booking payment" or "task payment". In your App Store Connect reply, quote 3.1.3(e) word for word. Add a 3-step path the reviewer can follow (post a task, accept a helper, pay for that task) and state that nothing digital is unlocked. If a stored balance is still needed (for example for refunds), make it refund-to-card only, with no other use in the app. The appeal and your reply run separately. Once you change the build or the wording, resubmit rather than waiting on the appeal.
Replies
Boosts
Views
Activity
1w