Tommy Jackson

After exchanging many emails with Zendesk support regarding this same issue, they told me they do support the new FCM API (V1), but could provide no guidance for how to authenticate in the Zendesk Admin Center without enabling the legacy api and using the `server key` it provides. I posted another issue here, so hopefully this problem will gain some traction soon.

The Android push notification integration in the Zendesk Admin Center requires the `sender id` and `server key` from Firebase. The `server key` value, however, is part of "Cloud Messaging API (Legacy)", which has been deprecated and will be fully shut down in June of this year in favor of "Firebase Cloud Messaging API (V1)". 

"Firebase Cloud Messaging API (V1)" uses a private key file in JSON format for authentication instead of the `server key` that the legacy api used. However, there is no option to upload this JSON key anywhere in the Zendesk Admin Center. For reference, another company that integrates push notifications similarly, Braze, has provided a spot to upload this new key along with a migration guide detailing the necessary steps for how to retrieve the JSON key and upload it.

Zendesk Support has told me multiple times now that they do indeed support "Firebase Cloud Messaging API (V1)", but they followed that up by sending me steps for how to enable the legacy api, and retrieve the `server key` and `sender id` from that. There is no equivalent string `server key` for "Firebase Cloud Messaging API (V1)", and without the ability to upload the JSON file key to the Zendesk Admin Center, it seems to me that push notifications for all Android apps using Zendesk will stop working in June if this doesn't change.

After being unable to provide me with any helpful or relevant info, support told me to submit an issue here, so hopefully this will reach the necessary folks at Zendesk that can provide an estimate for when "Firebase Cloud Messaging API (V1)" Android push notification support will be added to the Zendesk Admin Center.

Greg Katechis Hi, we're still facing this problem. Specifically we need to be able to change the toolbar text color, but its hardcoded to #ffffff (white) in zs_request_toolbar_content.xml, which is included in zs_activity_request.xml. 

We've tried following the steps here, but as stated above by Josh it seems like every custom UI component in those files is marked with @RestrictTo(LIBRARY), which prevents us from accessing and using them. We can't copy the layouts like your docs say to do without those components or the functionality would break.

Messing with the theme doesn't do anything either because the text color is fully hardcoded to be white, and we can't even replace that single xml file because it uses zendesk.support.request.ViewToolbarAvatar which is one of those classes restricted to the library.

How can we change the toolbar's text color?