We are migrating over from Outlook API that is deprecated to Microsoft Graph API. We have a working flow where we are subscribed to a user's contacts changed/created/deleted events.
I created a subscription and got back a 201 response and the following:
{"#odata.context":"https://graph.microsoft.com/beta/$metadata#subscriptions/$entity",
"id":"xxxxxxx",
"resource":"me/contactFolders/YYYYYYYYYYY/contacts",
"applicationId":"ZZZZZZZZZZZZ",
"changeType":"created,updated,deleted",
"clientState":null,
"notificationUrl":"https://xxxxxxx.com/xxxxxxx",
"notificationQueryOptions":null,
"notificationContentType":"application/json",
"lifecycleNotificationUrl":null,
"expirationDateTime":"2022-05-21T17:05:09Z",
"creatorId":"444444444444",
"includeResourceData":null,
"latestSupportedTlsVersion":"v1_2",
"encryptionCertificate":null,
"encryptionCertificateId":null,
"notificationUrlAppId":null}
However, I've tried to subscribe to just "me/contacts" instead of a specific folder as well but no matter what I do, my notification URL does not receive any notifications. I have subscriptions for email messages and that one works fine. Is there something that is different with receiving notifications from the old Outlook API vs Microsoft Graph's subscription notification?
Related
I subscribe the chat message about a chat session,and I can see subscription info on "/subscriptions" API,but can't receive any notify on notify URL recently.
Everything was normal before today.Maybe I send message too fast? When it happened,
I can not receive notify any more,what should I do.
We create an application that receives notifications that there was a call. For this we create a subscription (communications / callRecords) to receive notification.
My question is, if there are errors when renewing the subscription, then all the notifications that occurred when the subscription was inactive will be lost?
Also I found that we can use Azure Event Hub (Get change notifications delivered in different ways) to send notifications to the hub and then read data from it, but for this case we need to keep subscription up-to-date?
Is there a way to guarantee receiving notifications?
I'm working with AWS SNS API for mobile notification,
along with AWS CloudWatch for message monitoring.
There's currently only 5 metrics to be watched:
NumberOfMessagesPublished
PublishSize
NumberOfNotificationsDelivered
NumberOfNotificationsFailed
SMSSuccessRate
None of these seems to be like message content, recipient platforms, or delivered date/time. (contents that make more sense to marketers rather than developers)
How could I query the history of all my sent messages or a specific message?
SNS does not retain sent messages. You would have to archive the sent messages yourself as you send them.
One idea is to let SNS itself do the message archiving for you, so that you can then query the archive for the analytics that are relevant to you.
This can be done by subscribing a Kinesis Data Firehose to the SNS topic that you use for sending these mobile notifications. You can configure your Firehose stream to store the SNS notifications in S3, Redshift, Elasticsearch, Datadog, Splunk, New Relic, or MongoDB.
Check this out: https://aws.amazon.com/about-aws/whats-new/2021/01/amazon-sns-adds-support-for-message-archiving-and-analytics-via-kineses-data-firehose-subscriptions/
SNS is a wrapper around a number of similar notification APIs. The APIs for Apple (APNS) and Google (Most Android) GCN don't offer any kind of receipt confirmation.
If you need receipt confirmation you would have to build that into the application on the mobile device to inspect messages received that were for that application and there is no universal way to do that either. The other issue is that you are totally at the mercy of the user authorizing notifications.
I suggest you incorporate messaging of your own inside the app and have push notifications as an optional enhancement. In order to get badges to work right you also need cooperation with the app since there is no way using SNS to react to actions taken in the app to clear the notifications or adjust the badge value.
I am working on a chat using XMPP Protocol. Everything is working fine using XMPP. But I'm unable to receive offline messages from agent when user comes to online. As user A is logged out and user B sends messages to user A, and when user A logs into app, it must receive all the messages that were sent by user B during offline session. How can I receive these messages?
With rooms you can do this easily by joining the chat asking history since the time you went offline. For one-to-one chat, you will have to implement per user offline queue at the server end. And notify server once you are online to receive the chats.
I am create a firebase based chat application for iOS. One of the features is to send push notification to the users in the same chat room (if they are offline).
I can't find a firebase function (for iOS) that can be used to send push notifications to the user.
Is it possible?
Displaying alert badges and notifications on iPhone applications is accomplished through Apple's Push Notification system. Since the application is not running on the user's phone when they receive notifications, the APN will have to be triggered from your server-side code.
You'll probably want to create a server-side module that listens for changes to your chat Firebase. When a message appears for a user that is offline, you'll have to schedule a remote notification with the APN. That latter part has nothing to do with Firebase, but has extensive documentation on Apple's developer web site.
I'm not sure if a web application can display alerts or badges. Otherwise this approach will only work if you create a native wrapper for your Firebase chat application.