Add Logging to Detect FCM Message Deprioritization#12
Conversation
| int currentPriority = remoteMessage.getPriority(); // PRIORITY_HIGH = 1, PRIORITY_NORMAL = 2, PRIORITY_UNKNOWN = 0 | ||
|
|
||
| if (originalPriority != currentPriority) { | ||
| Log.e(TAG, "onMessageReceived: MESSAGE DEPRIORITIZED! originalPriority: " + originalPriority + " currentPriority: " + currentPriority); |
There was a problem hiding this comment.
is this collected somewhere that we can see?
how would this help us identifying problems unless the phone is being watched by a dev?
There was a problem hiding this comment.
We could additionally try to report errors/logs to Google play or appsignal or something.
This is still somewhat useful as we (devs) could attempt to run through reproduction steps, and use this to see what is happening to the message priority. Or if its someone like Sara or QA, we could (possibly) provide instructions on how to check logs.
Will try to think of something for that and propose something
There was a problem hiding this comment.
This is a general / existing problem with viewing android Logs against other people's including customers, QA, etc. devices.
I'll try to think of what we should do for that
There was a problem hiding this comment.
i use https://docs.appsignal.com/api/public-endpoint/errors.html in google-calendar add-on to collect data (created a separate appsignal "environment" for this purpose)
maybe it's an option for you too.
There was a problem hiding this comment.
Looking into this (sorry for the delay)...
2 participants
So far not yet happening but if / when this happens there will be consequences.
This will allow us to detect that the message was deprioritized and what happened to its priority level.