Question 105994 in Azure Question posted in
The official documentation to get you started can be found here.

Firebase Cloud Messaging (FCM) Api Key for Azure Notification Hub

I’m creating a Xamarin project to test Azure Notification Hub, but I’m having trouble going through the steps in this article

Under the section "Create a Firebase project and enable Firebase Cloud Messaging"
Step 6 is obsolete as Google seems to have changed their model to obtain a Server Key, or the Server Key does not apply to FCM.

Can anyone shed a light on how to obtain an Api key for Azure Notification Hub?

Tags:

3

Answers


  1. 0

    If you go to the Build section, Authentication menu item, and then click the ‘Get Started’ button, then navigate back to the Project Settings/General tab, you should see the API key.
    EDIT: This is not the proper key for the Azure Notification Hub. See my comment below for the correct key.

    Login or Signup to reply.
  2. 0

    expanding DrDave’s comment

    From https://console.firebase.google.com/project/--your_project_name--/settings/cloudmessaging

    • Click on the three-dots menu of the "Cloud Messaging API (Legacy) 🚫 Disabled" Heading
    • Follow the offered link to manage in google cloud console, and there press the button to enable the googlecloudmessaging API
    • Wait a few minutes
    • Go back to your Firebase console Cloud Messaging Tab, and refresh.
    • See that the Cloud Messaging API header has changed to "Cloud Messaging API (Legacy) ✅ Enabled" and that a Server Key is now shown.
    Login or Signup to reply.
  3. 0

    There currently does not seem to be a proper answer to this.

    When using FCM, if you head to the Authentication page on the Firebase Console for your app and select ‘Get Started’, follow the steps and then head back to the ‘General’ tab in your project settings page, you will see that it now has a Web API key.

    This isn’t useful for Azure Notification Hubs as if you try insert this key into the API key entry for a hub, it will not accept it.

    The only answer seems to be to use the legacy GCM API, which is not ideal as it has been deprecated and certain APIs are no longer available.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search