Dealing with Rejected and Flagged Apps
Every seller on Console Logs wants their apps to be successful, but sometimes, you might face challenges such as a rejected submission or a flagged app. Understanding why these issues occur and knowing how to address them can help you get back on track quickly. Here’s a guide to navigating these situations:
Rejected Apps
- Why an App Gets Rejected: Apps can be rejected during the review process for various reasons, such as not meeting content guidelines, having incomplete information, or containing errors. The specific reason for rejection is typically provided along with feedback from the review team.
- What to Do When Your App is Rejected:
- Review the Feedback: Carefully read the feedback provided by the Console Logs team. This feedback will give you insights into what went wrong and what changes are needed.
- Make Necessary Changes: Update your app based on the feedback. This could involve fixing bugs, adding missing details, or ensuring that your content meets the platform’s standards.
- Resubmit Your App: Once you’ve made the required adjustments, you can re-submit your app for review. Ensure all changes are implemented to improve the chances of approval.
- Tips to Avoid Rejection in the Future:
- Follow the Submission Checklist: Always refer to the App Submission Checklist before submitting your app. This helps ensure you’ve covered all the important aspects.
- Double-check Content: Verify that all descriptions, screenshots, and other information provided in your submission are accurate and complete.
Flagged Apps
-
Why an App Gets Flagged: An app can be flagged after it has been published if an issue is found later, such as a policy violation, misleading content, or user complaints. This means that while the app was initially approved, a problem has been detected that needs to be addressed.
-
What to Do When Your App is Flagged:
- Understand the Issue: Our team will typically provide a reason for why your app was flagged. This may include details on the specific violation or complaint.
- Fix the Problem: Address the issue identified by the team. It might involve correcting content, or updating the app to comply with platform policies.
- Re-submit for Review: After making the necessary corrections, re-submit the app for review. Make sure to explain the changes you made in the “What’s New” section for transparency.
Existing Customers Still Have Access: If a customer has already purchased your app before it was flagged, they will continue to have access to it. They can view and use the app as before, but no new purchases can be made by other users.
-
Tips to Avoid Being Flagged:
- Keep Your App Updated: Regularly update your app to fix any bugs or security issues that might arise over time.
- Adhere to Platform Policies: Ensure that your app and its content always align with the guidelines set by Console Logs.
- Be Transparent with Users: Clearly communicate any changes or updates to your app in the “What’s New” section. This can help reduce misunderstandings that could lead to complaints.
Learning from the Process
- Stay Positive: It’s normal to feel discouraged when an app is rejected or flagged, but try to see it as an opportunity for improvement. The feedback provided can help you create a better product in the long run.
- Reach Out for Support: If you’re unclear about the feedback or need further guidance, don’t hesitate to reach out to our support team for clarification. They’re there to help you succeed.
- Improve for Future Submissions: Use the insights gained from rejections or flagging incidents to improve your future submissions. The goal is to refine your process so that each new app you submit has a smoother path to approval.