Create Android OAUTH client fails with: "An unexpected error occurred. Please try again later. (4800001)" - google-play

So I am trying to setup Google Play Games Services in the Google Play Developer Console.
This worked for me yesterday.
Today however, when setting up another app, and trying to link an android app to the games services, I get this error:
An unexpected error occurred. Please try again later. (4800001)
I got this in:
Google Play Developer Console -> Games Services -> [game] -> Linked Apps -> STEP 2 Authorize your app.
This happens regardless which key I try, my release key, or my debug key.
I don't understand why this would be happening, as it was working yesterday, albeit for an app without real-time multi player. The app I am trying to setup now needs real-time multiplayer, but I'm not sure whether this difference is the cause of it. Maybe servers at google are down?
I get the error each time I try, regardless which browser I use, or which OS. I tried on Ubuntu Firefox and OSX Safari.

This was a temporary breakage in the Google Play Developer Console.
They fixed it today, by rolling back changes to the console, see:
https://github.com/playgameservices/android-basic-samples/issues/153#issuecomment-134749998

I opened https://console.developers.google.com/ page and successfully registered my app there while I was having same issue as you.

Related

Is Google play console logs offline crashes when back to online

I published my mobile app in Google play console recently. Regarding crash logs in Android vitals I'm doing bit investigation on it and I have some doubts,
Is Google play console capable of log offline crashes when device back to online ?
I could see the crashes updated in Google Play console even I'm working in development apk with my real mobile device, How Google Play console logs the crashes occured it local apk, it is only for the apps downloaded from Google Play store right ?
Please anyone clarify my above questions since I'm new to mobile app development area
.
Yes, Google will collect crashes even when they occur offline.
Google will collect crashes even if the app is not installed via Play Store. You can however filter those crashes in the Play Console directly by adding the filter "Installed from Google Play":

Unknown error when creating a new project in Google API

I am getting this error when I try to create a project in console.developers.google.com. I have 8 more projects left in my quota. I have tried different names and different project IDs. When I hit the "retry" button it shows the error after some time again.
UPDATE [Oct 9, 2017]: It looks like Google fixed the issue, since I was able to create a new project today.
I went ahead and attempted to create a new project in the Google API, and received the same error. This has occurred before with the Google API and is considered a temporary issue, often being fixed the same day. But if I remember correctly they have had it down longer in the past.
So the good news is, it's not something that is on your end, the bad news is, it's on Google's end.
If your google account is a Google Apps account (Google Suite, Google Apps, Gsuite, or whatever the Marketing folks are calling it these days), then you need to enable "Google Developers Console".
Login as an admin to admin.google.com
Go to Apps > Additional Google services
Find the "Google Developers Console" line item and set to "ON for everyone" (or whatever).
That should do it.

error after flashing genymotion with google play (Google+ error)

I flashed my genymotion device and after, I got this error.
"An error occurred during the installation of google+ Please uninstall the app and then install it again"
To elaborate.
I created a new device, this one at the top highlgihted.
Google Nexus 4 5.0.0 API 21
I read this good and (as of writing), up to date answer here about installing google play services on it Google Play Services in Genymotion on Lollipop (Android 5.0)
So I started it, did adb devices saw the device listed there.
Dragged this on Genymotion-ARM-Translation_v1.1.zip
I did adb reboot
I dragged this on gapps-lp-20141109-signed.zip
I did adb reboot
Then I got this screen (it looked good though I knew it might not work so I took a screenshot as "evidence"!)
Then on going to google play store, or on unlocking the screen.. and periodically..or whenever it is, I got/get this screen
It did ask me to register with google signing or or creating a new account when going into the play store, and I did. Though I still get that google+ error message from time to time.
I can use android studio's emulator api 21 in the meantime as while it doesn't have google play store, it does seem to have google play services such that various apps can run, but i'd be interested in having genymotion running without error with google apps services too, particularly as having the google play store, as it does, is good so if it can be without this error then all the better.
You need to be patient through the error messages, and manage to sign-in to the play store and update Google+.
After, you should get a notification saying you need to update Google Play Services, do it as well.
It can be annoying with the error message popping all the time but you just have to go through this once :).
Reboot the device after and it should work.

Pebble.js WatchApp displays: "Disconnected - run the pebble phone app"

I can't find much documentation around this issue. All other running apps on my pebble have a connection to my phone, and work as expected. However, a Pebble.js application I'm currently working on simply displays Disconnected - run the pebble phone app.
I have noticed that in my Developer Settings that the Connection Manager is listed as Disconnected. Is this part of the problem? I see nothing in the logs.
For reference, the application is doing a simple ajax request and displaying the result.
This message is often caused by the JavaScript crashing on the phone (undefined reference, unknown function, etc) and so the watch thinks it is not running.
Some ideas to debug this:
Replace your code with one very simple console.log("hello world") statement and see if this works.
Look at the Logs (View Logs button in CloudPebble or pebble logs on the command line).
Very rarely, on Android, I have seen situation where the Pebble app is in a bad state where it cannot execute the JS for only one app. When this happens, you need to force-kill the Pebble app and relaunch it.
I have had the same experience.
I usually kill and restart the pebble app on my phone and then I also do refresh the browser. Sometimes you have to log out of and then log back into Cloudpebble.

App approved, but crashes

I have made a Windows Phone app (for WP7.1) that uses BackgroundAudio for streaming, nothing too complicated. It was approved and made available for download in the store. However it no longer works, i.e. the app worked in debug+release when run from VS2012, and I assume the .xap I uploaded worked since microsoft approved it (they rejected it once and I was able to reproduce and fix the bugs they reported).
When downloaded the app simply bails on load on WP8 (lumia 820) i.e. flips back to the tiles immediately.
On WP7 (lumia 800) but the playbutton ignores input, however it downloads and displays the playlist, so some kind of functionality+network connection works.
I have tried the basics: installing using the application-deployment tool (app working), running the "Store Test Kit" which reports some slowdowns in the UI animations, but nothing serious (I hope).
Any ideas how to reproduce ".xap approved and downloaded from store but not working" or getting debug info from the phone without VS? Or any other things i can try out?
Every time your app crashes it will be logged and reported on your Windows Phone Dev Center Account. Just go in there and export the details to excel. Get the stack trace and put it in here. Maybe we can help.
The very first thing i can tell you is the opening page has some exceptions and that too it doesn't go well with some phones. Seriously there are concerns when a wp7 app is ported on wp8 device and vice-verse. To the extent of my knowledge there might be some binding issues. make sure you got the binding class to be public. And just as #AMR mentioned go the dev center and export the stacktrace. Try resolving them. Moreover if an app get certifies, it doesn't mean it is completely error free. The tests are limited to very coomon errors only.

Resources