Could not Configure the Firebase Cloud Messaging (FCM) push notification in embedding Zendesk in your Android app

Hi there! I'm not certain what you're referring to, with respect to the client email. Our documentation for setting up push notifications is available here and I don't see any mention of client emails. Could you explain what it is that you're running into a problem with in more detail?

I am running into a similar issue - after adding in the Project ID, Private Key, and Client Email, I receive a ‘Something went wrong, give it a moment and try again’ error. After inspecting the page, I see a push_credentials error with the status code of: 503 Service Unavailable. 

Wondering if there's a simple explanation for this error and a solution for how to fix this. Thanks!

Hi, 

Same here, following Zendesk email to change our deprecated Push Notification apikey to the new system :
 

(your email)
If you’re using Zendesk’s Messaging Android SDK: 
- Sign into Admin Center under your business subdomain: <your-subdomain>.zendesk.com/admin. 
- Click Channels in the sidebar, then select Messaging and social > Messaging. 
- Click the name of the Android channel to edit. The Edit Web Widget page opens. 
- Click the Notifications tab. 
- Enter the new credentials: privateKey, clientEmail and projectId. 

I followed each steps, but each time I submit the form with valid data I receive a 503 : 

PATCH https://<OUR_ZENDESK_SUBDOMAIN>.zendesk.com/admin/api/private/sunshine/conversations/mobile_sdk/<OUR_ID>/push_credentia

503 Service Unavailable
{
   "error": "UpstreamError",
   "message": "500 Internal Server Error: {\"error\"=\u003e{\"title\"=\u003e\"We're sorry but something went wrong\", \"message\"=\u003e\"We have been notified of this error and will be investigating it. If you see this error frequently, check the Zendesk status page at https://status.zendesk.com\"}}"
}

Deadline is 21 June, I hope you will fix this before this date !
Thanks !
 

@thibaud 

I'm not sure if this will work for you, as well, but I was able to get this to work. 

One of our developers found that when generating the private key, we had to paste the full private_key and not the private_key_id. The private_key that was generated was a very long string of letters, numbers, and special characters, starting and ending with: "-----BEGIN PRIVATE KEY-----  and -----END PRIVATE KEY-----\n". 

Once I pasted the full string into the Private Key field, I was able to submit without receiving the error. 

Hope this helps!

@maggie12 Thank you !

To make it works I had to copy/paste the full string with “ to keep the \n in it. Then I removed the leading and the trailing " character and it worked. The privateKey must contains \n to work… :/