'Start rollout to beta' disabled in Play Store Developer Console

Question

I am ready to send my first app to beta testers, so i click on \'Manage Beta\' > \'Manage testers\'

Answer 1

Saranga is right from my experience. Before I could send out a beta version I had to ensure I had the images under store listing included. Just look at the side bar (see image) and see whats greyed out and thats where the problem was for me.

Answer 2

Update : The answer below is outdated. These days you should see a list of options on the left, that have grayed out ticks in-front of them. Hover over the tick and it should display the list of tasks you need done to complete that category. Visit each of these items and complete them (make sure the icon becomes green - check the screenshot below) to enable the button.

Not sure whether this is the actual answer or what you are expecting, but I am stuck at the same place (I just created an account, application and a release. Saw the disabled button and started googling). However there is a link on the top right side of the screen (barely visible, i should add), with the text "Why can't I publish?". And when I click on it I get list of error messages(I think). So as of now i am stuck on that list. Probably, fixing them might enable the button.

Answer 3

I had same issue. In addition of all this you need to tick App Content tab also . Check out the details : here

Answer 4

You also need to make sure that you made it available in at least one country. By default not one country is selected!

Answer 5

If this is your first app, the problem will be due to payment processing which can take up to 48 hours according to your Google Play Developer Console under Account Details. Here is the actual text:

Payment Pending

Your payment is still processing, which will take up to 48 hours.

You can already start to upload APKs and prepare Store listings but not publish any applications yet.

We will notify you when the payment went through and you can publish your applications.

Answer 6

I had the same problem. In my case I had to agree to "Content guidelines" and "US export laws" listed under "Consent" in "Pricing & distribution" section.