My app was approved for production, and my first 4 to 5 updates were approved within hours. However, on my 6th update — I made a single string update — the review process took 5 days. I was surprised by the unusually lengthy time, but I waited patiently. Unfortunately, this update was rejected for the first time. The stated reason was a violation of the “Broken Functionality policy.” Here is a screenshot of the email I received:

I am going through the verification of the Google Play Console developer account. Account verification is required for all existing Google Play developers, who created their Play Console Account before September 2023. In the contact information, I entered the phone number correctly, the country code is +7, but an error appears: We can’t verify your phone number right now. Try again later. Please help me solve this problem for the phone number with the country code +7, why is there such an error?

I’m developing an app for my company and I’m in the process of publishing it to the Google Play Store. The app has two different layouts: one for vendors and another for users. After logging in, the app navigates to the vendor UI if the account is a vendor account, and to the employee UI for employee accounts.

After creating a Google Play release, I found the following problem specified by the pre-launch report.

I uploaded an app to the Google Play Store about a year ago. I then started working on many more features and improved the app tremendously but in the meantime, I did get a few installs but people uninstalled it right afterwards because there was no activity or any reason for people to keep the app installed.

After we updated the privacy policy and submit version 2 of our app, app not approved in two days.

I’m encountering a new issue with my team. We recently attempted to publish an update for our application, but it was rejected for not complying with the FOREGROUND_SERVICES usage policy. It seems we had omitted the necessary usage details for this permission in our Play Store listing. After adding the required information and resubmitting, the update was accepted, and it’s currently at a 5% rollout.