Develop Reference

How to add user properties to Service Bus topic output from Javascript Azure Function

I'm working on a TypeScript Azure Function that has an Azure Service bus topic as its output. I can send messages with it without any problem, but I cannot set any metadata as custom property on the message.
I've tried using an object with the same interface as the ServiceBusMessage from the Service Bus Javascript SDK, like this:
import { AzureFunction, Context, HttpRequest } from "#azure/functions";
const httpTrigger: AzureFunction = async function (
context: Context,
req: HttpRequest
): Promise<void> {
const message = {
body: "my message content",
applicationProperties: { key: "value" },
};
context.bindings.myTopic = message;
};
export default httpTrigger;
But the message is sent as-is, and the applicationProperties is not taken into account. I cannot see them on the Azure Portal in the Service Bus Explorer. The content of the message will be the JSON version of the message object.
I've tried with the extension bundles 3 and 4, without success.
I'm using this function.json file:
{
"bindings": [
{
"authLevel": "function",
"type": "httpTrigger",
"direction": "in",
"name": "req",
"methods": ["get", "post"]
},
{
"type": "http",
"direction": "out",
"name": "res"
},
{
"name": "myTopic",
"type": "serviceBus",
"queueName": "myTopic",
"connection": "SERVICE_BUS_CONNECTION_STRING",
"direction": "out"
}
],
"scriptFile": "../dist/servicebus-writer/index.js"
}
And this host.json file:
{
"version": "2.0",
"logging": {
"applicationInsights": {
"samplingSettings": {
"isEnabled": true,
"excludedTypes": "Request"
}
}
},
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle",
"version": "[3.3.0, 4.0.0)"
}
}
How can I set those custom properties?

As of today, there is no way to set metadata using bindings in non-C# languages. The workaround would be to use the Service Bus SDK directly to send out messages.
There is this feature request that you could up vote to gain more traction.

Outlook web add in with Graph API - Inline images not displaying when sending current item as an Outlook Item attachment

I am able to send my current item as an attachment , but i am running into a problem where if there are any inline images within my current item, These do not display properly when i open my current item as an attachment from my newly sent/received mail. I understand that the image src is incorrect after sending my original email as an attachment, but im not sure how to rectify this or if this is expected behaviour because i have missed something.
My aim is to forward my current item/email as it appears, as an outlook item to the recipients mailbox.
Im wondering is there an error in how i have set up my json which i post to the Graph API to send mail ? i will post it below incase anything stands out as being set up wrong. Thanks in advance!
var email = client.api('/me/messages/' + restID).get();
var attachments = client.api('/me/messages/' + restID + '/attachments').get()
const sendMail = {
message: {
subject: 'This contains my original email',// forwardMailSubject,
body: {
contentType: "Text",
content: 'Test' // forwardMailBody
},
toRecipients: [
{
emailAddress: {
address: 'test12321#outlook.com' //forwardMailbox
}
}
],
attachments: [
{
'#odata.type': "#microsoft.graph.itemAttachment",
'name': "attachment",
'contentType': "html",
'item': {
"#odata.type": "#microsoft.graph.message",
"id": email.id,
"createdDateTime": email.createdDateTime,
"lastModifiedDateTime": email.lastModifiedDateTime,
"receivedDateTime": email.receivedDateTime,
"sentDateTime": email.sentDateTime,
"hasAttachments": true,
"internetMessageId": email.internetMessageId,
"subject": "Reminder - please bring laptop",
"importance": "normal",
"conversationId": email.conversationId,
"isDeliveryReceiptRequested": false,
"isReadReceiptRequested": false,
"isRead": false,
"isDraft": false,
"webLink": email.webLink,
"body": email.body,
"sender": email.sender,
"from": email.from,
"toRecipients": email.toRecipients,
"attachments": attachments
}
}
]
}
};
client.api('/me/sendMail')
.post(sendMail);

Agora cloud recording is started successfully but not recording

Steps:
Acquire: success, got resourceId
Start: success, got sid
query: first got success but then, code 404
From the browser, I have joined with 2 users in a channel test1 and uids are 100 and 101.
For recording, I got resourceId for recording using uid 99 (On backend side)
//Accquire
let reqBody = {
"cname": 'test1',
"uid": '99',
"clientRequest": {}
};
Then I hit start API.
//start
let reqBody = {
"cname": 'test1',
"uid": 99,
"clientRequest": {
"token": channelRecorderToken,
"storageConfig": {
"secretKey": ("awsSecretKey"),
"region": storageRegion,
"accessKey": ("awsAccessKey"),
"bucket": ("awsBucket"),
"vendor": storageVendor,
"fileNamePrefix": [
"RECORDINGS"
]
},
}
};
AWS settings are correct, I checked multiple times. For generating token I used this,
let channelRecorderToken = RtcTokenBuilder.buildTokenWithUid(appID, appCertificate, channelName, userId, role, privilegeExpiredTs);
QUERY RESPONSE:
// RESPONSE 1
{
"resourceId": "resourceId",
"sid": "sid",
"serverResponse": {
"status": 4,
"fileList": "",
"fileListMode": "string",
"sliceStartTime": 0
}
}
// RESPONSE 2: When I again hit query API after 5-10 seconds
{
"resourceId": "resourceId",
"sid": "sid",
"code": 404
}

Setting up a webhook without Google Cloud Project

Want to set up the webhook on my pc and not on google cloud project like the guide is sugesting, and I'm not quite sure how to.
This is the guide: https://dialogflow.com/docs/getting-started/basic-fulfillment-conversation
It says to create a index.js with the following code in it
/*
* HTTP Cloud Function.
*
* #param {Object} req Cloud Function request context.
* #param {Object} res Cloud Function response context.
*/
exports.helloHttp = function helloHttp (req, res) {
response = "This is a sample response from your webhook!"
//Default response from the webhook to show it's working
res.setHeader('Content-Type', 'application/json');
//Requires application/json MIME type
res.send(JSON.stringify({ "speech": response, "displayText": response
//"speech" is the spoken version of the response, "displayText" is the visual version
}));
};
Never seen exports. before. The guide wants me to do something with 'google functions' and make one called hellohttp or something. Trying to figure out how to do it without google cloud projects.
I installed Node.js and created that file. I set the webhook url to https://my_ip/index.js but doesn't work. Not really sure what to do
this is the JSON I get
{
"id": "9c244834-3ee9-4291-98fd-aab8e975fb1f",
"timestamp": "2018-02-22T23:11:34.067Z",
"lang": "en",
"result": {
"source": "agent",
"resolvedQuery": "weather TOMORROW in VIRGINIA",
"action": "",
"actionIncomplete": false,
"parameters": {
"date": "2018-02-24",
"geo-city": "Virginia"
},
"contexts": [],
"metadata": {
"intentId": "44486050-dfd5-4c35-bcbf-4e168379df28",
"webhookUsed": "true",
"webhookForSlotFillingUsed": "false",
"webhookResponseTime": 5006,
"intentName": "Weather"
},
"fulfillment": {
"speech": "I don't know about the weather for 2018-02-24 in Virginia. Sorry!",
"messages": [
{
"type": 0,
"speech": "I don't know about the weather for 2018-02-24 in Virginia. Sorry!"
}
]
},
"score": 1
},
"status": {
"code": 206,
"errorType": "partial_content",
"errorDetails": "Webhook call failed. Error: Webhook response was empty.",
"webhookTimedOut": false
},
"sessionId": "9cdbd5bc-403e-4840-8970-e420f27d23e2"
}

Firebase messaging.setBackgroundMessageHandler not receiving messages

I am trying Firebase Cloud Messaging. It's awesome and all, but I am having the hardest time getting it to work for me.
The problem I am facing is with the service worker, here is my firebase-messaging-sw.js :
console.log('Service worker is loaded!');
self.addEventListener('install', function(event) {
console.log('Service Worker is being installed.');
});
self.addEventListener('activate', function(event) {
console.log('Service Worker is being activated.');
});
importScripts('https://www.gstatic.com/firebasejs/3.6.5/firebase-app.js');
importScripts('https://www.gstatic.com/firebasejs/3.6.5/firebase-messaging.js');
firebase.initializeApp({
'messagingSenderId': ' ... '
});
var messaging = firebase.messaging();
messaging.setBackgroundMessageHandler(function(payload){
console.log('Received background message: ', payload);
return self.registration.showNotification('Title', {'body': 'Body'});
});
When I send a message (I am using PHP-FCM BTW) the message gets received as expected in the browser when the page is under focus, through onMessage( ... ), but never when the page isn't under focus or the browser is closed; the service worker just doesn't receive the message!
The line "Received background message: ... " never shows; meaning that the message handler wasn't registered at all!
Here's a sample message response:
{
"from": " ... ",
"collapse_key": "do_not_collapse",
"data": {
"id": "111"
},
"priority": "high",
"notification": {
"title": "Hi there",
"body": "Message body",
"badge": "1",
"color": "#ffffff"
}
}
What could be the issue here? It's driving me crazy.

No it is registered but not invoked because of the way you choose to structure your notification. Referring to the FCM docs:
https://firebase.google.com/docs/cloud-messaging/js/receive
"Note: If you set notification fields in your HTTP or XMPP send request, those values take precedence over any values specified in the service worker."
So, you have
{
"from": " ... ",
"collapse_key": "do_not_collapse",
"data": {
"id": "111"
},
"priority": "high",
"notification": {
"title": "Hi there",
"body": "Message body",
"badge": "1",
"color": "#ffffff"
}
}
and this structure never triggers the BackgroundMessageHandler. Because sending data this way, simply overrides your variables. If you want to trigger it you need to send your notification like this:
{
"from": " ... ",
"collapse_key": "do_not_collapse",
"priority": "high",
"data": {
"id": "111",
"notification": {
"title": "Hi there",
"body": "Message body",
"badge": "1",
"color": "#ffffff"
}
},
"to": "topic",
}

I'm not sure that you can define the imports roots in the middle of your javascript, I think those calls need to be at the top.
Also the badge value and color are not supported by the FCM SDK. If you want to set the badge you can use the background message handler to show a notification use the normal APi and define the badge through that APi