It is normal for Google developer accounts to be blocked, apps to be removed from the shelves, and bags to be rejected.
Here are some common causes of the problem:
1. The application is judged as a vest package: the title is blocked due to the high similarity with other products in the store in terms of code, UI, and application description.
(1) High similarity in code structure: high similarity in framework encapsulation; naming rules such as class names, method names, and variable names are unique; the same domain name is used; a lot of third-party frameworks are used, etc.
(2) High UI similarity: Many pictures and icons have been used; the interface, theme, layout, etc. are highly similar to other products.
(3) App logos, store promotional images, and text descriptions infringe upon or plagiarize others.
solution:
Modify potentially repetitive parts of the code, UI, and store. (In order to reduce the risk of being blocked again, try to redesign)
Class names, method names, variable names, etc. should not be unique when naming
2. Account registration related issues:
(1) The used high-risk account is associated with the main account;
(2) The test account has tested the problematic product;
(3) Multiple newly registered accounts are associated with the main account.
(4) Test existing products on devices with blocked accounts.
(5) Receipt and payment information (association of payment data) is bound to an account with high risk.
solution:
Standardize the application and use of accounts; it is not allowed to use newly applied accounts; purchase a stable old account as the main account, use a fixed VPS to log in for a period of time, and then operate; test accounts do not use multiple mobile phones to log in; try to log in with one device A test account, and a test account is bound to a main account.
3. IP problem. The IP of the account has been changed multiple times, such as using a VPN to log in to the main account and changing the VPN node multiple times;
Suggested solution:
Do not use a VPN to log in to the main account, use a VPS. Do not change the IP of the test account multiple times;
4. The application is judged as a violation project. (Because of being complained, being judged to be pornographic and third-party payment, etc., it was blocked after being removed from the shelves many times)
Suggested solution:
After discovering that the app has been taken off the shelf, do not update the package immediately, stop for two days, and then update it. According to the specific modification given by the store, the location of the problem needs to be refactored.
Reasons and solutions for the rejection and removal of the Google Play Control Center application review:
3. Removal due to complaints:
(1) If there are too many negative reviews, if there is a slight user complaint, it will be targeted by Google and lead to removal from the shelf.
(2) Removal due to too many complaints.
Commonly used in paid apps, the user’s payment experience is poor, and there are many refund disputes
Suggested solution:
(1) Actively and promptly reply to various comments of users on the Google store, and actively handle user refunds and after-sales disputes.
(2) Set complaint, report, customer service, contact us and other portals in the app to reduce users' negative reviews or complaints in the store.
Suggested solution:
(1) Refactor payment-related codes;
(2) Load the third-party payment in the form of webView.
(3) Shield the location of the Google office.
5. Removal caused by pornographic and violent images:
There are exposed/violent/bloody images uploaded by users in the app, which violates Google's rules.
Suggested solution:
Review the pictures uploaded by users, and the pictures that pass the review can be displayed to other users.
6. Warning of security vulnerabilities caused by Https:
This generally does not lead to delisting, and will appear in the form of a warning. However, if multiple warnings are not changed, it will cause delisting:
Suggested solution:
When verifying that the SSL certificate callback is invalid, a dialog box pops up, allowing the user to decide whether to continue to visit the webpage.
7. Security vulnerability warning caused by data transmission:
This will not be taken off the shelves immediately, but it will be rectified for you for a period of time. If the rectification is not completed within this period, it will be taken off the shelves.
Suggested solution:
Use the encryption method recommended by Google for data transmission.
7. The review caused by the Beta version was rejected:
There may be some warnings when using it. The official version will change the warnings, but sometimes the Beta will be forgotten and not changed, which may cause rejection when carrying the bag. The reason for the rejection is just that you have warnings and have not dealt with them. It is not stated that it is caused by the Beta version, which makes it difficult for developers to think that it is caused by the Beta version. So when the warning appears again, you must think about updating the Beta version of the package, or directly download the Beta version.