Error Creating json project configuration file for implementing GCM Client on Android

Question

I am trying to get gcm to work in my application. It is my task to update the application from the Eclipse build to the Android studio build. Android Studio no longer works in the build, just plug in gcm.jar, so I follow this documentation: https://developers.google.com/cloud-messaging/android/client to run my application with gcm.

To do this, I need to create a json configuration file. To make this file, I must provide the creator of the Google configuration file with my appId and my package name.

I entered them into the google form and after entering I get the error message: "There was an unknown error processing the request. Please try again."

This error message is very vague.

I tried again in Internet Explorer with the same result.

Perhaps there is an error with my appId and package name? How do I know? Perhaps this service has just come down, and I have to wait until tomorrow, but first I want to fix all my options.

My appId and package_name are "myCompanyName.android"

Answer 1

Recently it turned out that creating a client identifier for an application in the project of the developer console fixes this error and allows you to create a configuration file ...

Developer console projects APIs & auth Credentials Create new client ID: Installed application Android Enter package name Enter SHA1 for RELEASE OR DEBUG (which ever one you want it to work with) Make deep linking choice Create 

Then she returned to the page, and it works. Maybe there are other things in the console that you need to do, but idk, since I already have other settings.

Answer 2

Turns off a form that simply does not accept periods in the application name. I'm not sure why periods are acceptable in the application name in my assembly.

In any case, I will leave this question here if someone else runs into this problem because the error message is soooooooo undefined.

Answer 3

I have the same issue when logging in to Google using multiple accounts.

Only login using one account and problem will be allowed.

Answer 4

And for me, the solution was as simple as:

• exit Firebase
• log in to Firebase