CODEWITHSUNDEEP
google-play-console
Nikunj B Patel
Nikunj B Patel

Reputation: 199

what is this error "An unexpected error occurred. Please try again later. (8869003)"

i am unable to publish any apps on my Google Play Developer account is says An unexpected error occurred. Please try again later. (8869003) can anyone please help me to get out of this?

Upvotes: 19

Views: 33509

Answers (7)

LIU YUE
LIU YUE

Reputation: 2007

in my case it's due to the network issues that my laptop by default will use our company's system proxy, I guess it'll go through some internal firewalls before reach the outside world, the latency caused the error, i switched to no proxy mode, then everything working fine

Upvotes: 0

MZG
MZG

Reputation: 51

I faced this issue when update my developer profile on google play developer account. There is a featured app selection at the end of the page. I selected an app that is not published yet, caused the problem.

I didn't select that app as featured and it worked.

Upvotes: 0

live-love
live-love

Reputation: 52534

This happened to me as well. It could have been because I changed my account email on the same day. I got it working the next day.

Things to try:

  • Use a different computer.

  • You have to select at least one country from the list of countries to test.

  • Give it 24 hours for Google to refresh your email change, and try again.

  • If nothing works, contact Google Play Console Customer Support, they have a chat window.

Upvotes: 0

RhodanV5500
RhodanV5500

Reputation: 1107

I ran into a similar Android Developer Console Issue today. I was trying to promote a Closed Testing Track (Beta) to Production.

I always got the following error (with random error codes): An unexpected error has occurred. Please try again. (Random-Error-Code)

The solution was to create the new release by hand in the Production Track, rather than promoting up the existing Closed Testing Track.

Upvotes: 0

jleviaguirre
jleviaguirre

Reputation: 706

In used incognito window and worked. Clearing cookies, cache might also work

Upvotes: 3

Fawaz Chughtai
Fawaz Chughtai

Reputation: 41

It happens due to conflict between chrome signed in account and google console signed in account, signing out from console and resigning in will solve the conflict. Solaza suggested the same solution

Upvotes: 0

solaza
solaza

Reputation: 1291

Had same issue today. In my case I had to logout and login. Then everything worked.

Upvotes: 20

Related Questions