In App Center there are "Events" and "Log Flow". I have Events coming in (first picture), but nothing appears in Log Flow (second picture). What makes Log Flow show information?
Also, I am using TrackEvent such as...
Analytics.TrackEvent("Hello World");
'Log flow' shows the real-time events log.
So it works only while your app is running. Else it will show 'Awaiting data...'
If still no logs here while app is running - events sending is not working for this app.
'Log flow' in general used for testing app event sending (Is it send or not...)
Related
My app has an option to turn on/off FCM notifications.
I can not show FCM notification when the App in foreground.
But how to turn off the notification function of FCM when the App in background?
Turn off FCM functionality with code in Android Studio.
Firebase Cloud Messaging has two payload types in its messages:
Notification payloads, which is handled by the system itself if the app is not active, and can be handled by your code if the app is active.
Data payloads, which are always handled by your code. This code can then display a notification, but it can also do something else (or nothing at all) with the data.
If you send a Notification message and the app is not actively being used, that message is handled by the system and there's no way to prevent it from being displayed.
So you have two options:
Always send message with (only) a data payload, so that your own code can handle it - and display a notification if the user hasn't disabled that.
Don't send a message with a notification payload if the user has disabled receiving notifications.
Since connect api sends the response to the "listner api" IMMEDIETELY after the last recipient signs the document. If my "listner api" is down at that perticular time. How will I get the response again from connect api?
Does connect api provide any option to send it again?
You're looking for the option to Require Acknowledgement. As per the documentation:
Require Acknowledgement: Select this option to log posting failures.
The acknowledgement failure messages are logged in the Failures page,
which is accessed b clicking Failures on the DocuSign Connect Settings
page. When this option is selected, DocuSign will automatically
attempt to repost any failures. Alternately, you can manually repost
from the Failures page. See the Publish Failures section for more
information
As long as your application can return a 200 status code when it does successfully accept a Connect publish, having Require Acknowledgement on means that failures will be logged and retried.
The answer from Drew is correct, but here's some additional information: the Connect resend algorithm, used if require acknowledgement is on, does not try to resend immediately. And if the Connect Send Individual Messages (SIM) option is off (the default), then a message won't be resent if the message is superseded by another message about the same envelope.
Better is to not have your server (your "listener") ever go down. Best way to do that: have Connect send to AWS or similar, then your app pulls from AWS SQS or similar. See the code examples named connect- here: https://github.com/docusign
My Chrome Extension's background page is set up as an event page, i.e., most of the time it is asleep unless some registered event listener wakes it up.
I'd like to be able to occasionally send messages from my server to the event page of an individual user of my extension. They should not necessarily show up as a desktop notification, it would rather be up to the background script to decide what to do with any incoming message. It might very well store some information in localstorage for example. If the user client was offline at the moment the message is being sent, it would ideally be delivered once it comes back online.
I'd like to avoid polling my server at regular intervals every time the background script is awake, though that would be an obvious solution.
My question is therefore if it is possible to register a special kind of event in my event page so that it wakes up and triggers some functionality once there's an incoming message from my server. Ideally, the server message would not be a general broadcast to all my users, but rather a targeted message to a specific user.
What options do I have?
I read about service workers and their Push API but it seems they are only slowly being rolled out to Chrome Extensions. I am not sure if they are ready for the browser's stable release yet and didn't find any documentation on how they work with extensions.
I also read a bit about Google Cloud Messaging but it is deprecated in favor of a new costly Firebase solution.
Service worker functions like a proxy server, allowing you to modify requests and responses, replace them with items from its own cache, and more. While Chrome has its own approach to caching/installing the resources need to display a Chrome Extension. Therefore, there will be an error when you will attempt to intercept the registration of a service worker to a Chrome Extension.
See for more information:
Introduction to service worker
Service Worker script errors if run in chrome extension
See related SO post:
Chrome Extensions with service worker receiving push notifications
I have setup a Webhook to my development environment. In addition to receiving the event notifications which I would expect, I receive additional notifications (with unique event ID) which do not make sense to me. When I try to look up those events on the Stripe dashboard I cannot find trace of them... Shouldn't all events be logged on the Dashboard?
Has anyone experienced this? I've popped a mail to the support but no answer yet.
EDIT:
I could find one of the "missing" events on the dashboard now. It was buried far down the event list, as it was apparently fired several hours ago for the first time, but couldn't be handled at that time by my application.
All events appear on the dashboard, listed at the time they are fired for the first time. So in case the application receiving the notification can't return a response 2xx for some reason, Stripe will try sending the notification again at a later time. Once the application server handles the event notification properly, the event will in all likelihood be logged by the application, and the timing might look confusing.
I have inherited a basic Azure Web App as part of a system that needs to be very responsive. The system sends an HTTP POST to my Azure server which then processes the message and sends a response. Most of the time the server responds in about 0.4s which is fine however there are occasions when the response time jumps to several seconds.
I have instrumented the code and captured the time from when the POST is sent from my system to when the App first get kicked off by the POST arriving and the delay seems to be from the POST being sent to the App starting (not in the App itself). This is all in the working of Azure and I do not know of any way of getting any further metrics.
My Web App is always on with auto scaling I do not see any obvious problems on the Azure console. My tests send a POST every few seconds so I would not expect the App to go to sleep.