I have configured my Notification Hub with FCM and have configured my Android mobile app (running in Emulator) to receive notifications. The issue I face here is, If I send test notification from FCM I am getting the notification in Emulator but If I am sending the notification from Azure Notification Hub I am not getting the notification. I have configured as advised by the link (Assigned API Key with server key and legacy key). Also, I see that the Registration ID in the Test Notification is the registration ID of the running emulator also.
So what should I check now here? so that I can make notification work from Azure Notification Hub?
Are you using HTTP Trigger for triggering azure notification hub?
Because HTTP Trigger doesn't support FCM, it supports GCM (which is depreceated one)
So, Trigger Android using FCM
Related
I want to integrate Azure push notifications REST API in Mule 4. I have registered my device to the azure portal hub and I am receiving the notification when sending the notification directly from azure portal.
But when using the rest api from postman, I am not receiving it although it returns me a 201 CREATED response.
I am not targeting any tags. I tried direct send, gcm native. could not receive any notifications.
Direct Send API Headers
Direct Send API Body
Hi I have azure data factory which will be triggered by users which they are authenticated via azure ad implicit flow. ADF after the run will send events to service bus. Now I have to write azure function app based on the service bus trigger. In app function I want to send notification to users via signal r. But my problem is whoever triggered adf for them only I need to send notification. UI will trigger adf and adf will send events to service bus and in this flow UI will send user information to adf and adf will send user information to service bus event also. But In azure function app I want to send notification to only those user who triggered ADF.
public void BroadcastMessage(string message)
{
Clients.Caller.SendAsync("broadcastMessage", message);
}
Currently above code I am using in my other application which will send notification to web app. When coming to azure function app how can I send notification to only specific user who triggered ADF. I have seen several example with azure app service authentication but not with azure ad. My front end is currently having azure ad authentication and deployed in app service but I do not have app service authentication.Can someone help me is it possible or what would be the correct approach? Any help would be greatly appreciated. Thank you
The negotiate endpoint accepts a UserId parameter that could pass around to later identify the user to notify.
While the example is fetching the user identity for app service, you could leverage runtime binding if you are using C#. For non-C# languages, you could have an "internal" negotiate function that is called by the "external" negotiate function passing in the extracted user identity from the JWT token.
With this, you could extract the same user identity in the function that initiates the ADF pipeline passing this value, which ADF could include in the service bus messages it sends later on.
I have a C# echo bot developed in Visual Studio as per Azure documentation which runs successfully on a bot emulator in desktop. This bot was deployed to Azure and it wouldn't work in web chat or in the "Test in Web Chat" window in Azure portal. It always replies with - couldn't send retry. Could someone please help me out?
This post There was an error sending this message to your bot - Test in Web Chat suggested to check the Messaging endpoint specified and make sure it is same as your using in the bot emulator.
However messaging endpoint in Azure is like https://webappname123.azurewebsites.net/api/messages but in emulator endpoint is a local host http://localhost:3978/api/messages . How can these two match?
Also when I went into channels issue is like "There was an error sending this message to your bot: HTTP status code NotFound"
Is there any place where I could change endpoint URL?
I followed as it is process mentioned in Azure doc for building and deploying Echo bot
Have you added the correct Microsoft App ID and Microsoft App Password in your appsettings.json ?
Your Azure messaging endpoint in azure configuration should be the publicly accessible endpoint, when you are debugging locally, the emulator can authenticate using those Microsoft App ID and Microsoft App Password to reach your service.
When you deploy your solution your bot also authenticates using those credentials.
So make sure those credentials are correct and that your messaging endpoint "https://xxxxxx.azurewebsites.net/api/messages " is working publicly
When you publish your bot, there will be an option as below :
Select Edit App Service Settings.
Add the following details :
MicrosoftAppId : <xxxxx>
MicrosoftAppPassword : <xxxxx>
Click Apply, Ok.
Make sure you remove the Microsoft App Id and Microsoft App Password from appsettings.json, so that it works in bot emulator as well.
Now Publish the bot. It will work at both places.
Hope this is helpful.
I've set up a starterkit on studio.botkit.ai for Microsoft Teams. The bot is hosted on glitch. In Azure bot registration I've included the endpoint provided by glitch. Ive also added my id and password from azure bot registration to my bot.
When I try and test out the bot in azure web chat I sends an error that reads
"There was an error sending this message to your bot: HTTP status code NotFound"
It this possible?
Check to make sure the messaging endpoint URL configured in Azure matches your Glitch url for Botkit, which will include "/receive/teams"
Is it possible to create webhook in stripe account using API if we have client secret key of destination account?
No, webhook endpoints can only be created, edited or removed via the dashboard, not via the API.
EDIT: This is no longer true. Webhook endpoints can now be managed via the API: https://stripe.com/docs/api/webhook_endpoints.
If you want to receive events emitted from accounts that are connected to your platform, you need to set up a Connect webhook endpoint on the platform's account, not add endpoints to each connected account. See the documentation here for more information.