You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's something that could happen at the application-services level.
But, basically, when #28 is implemented, the .sync() method has to be called with the timestamp received via the Push notification.
The broadcast id is "remote-settings/monitor_changes" and the timestamp is sent with the format of an ETag (eg, surrounded with quotes: "{timestamp}").
In Telemetry, we distringuish the different scenariis of synchronization using a "trigger" field ("manual", "startup", "broadcast")
That's something that could happen at the application-services level.
But, basically, when #28 is implemented, the
.sync()method has to be called with the timestamp received via the Push notification.The broadcast id is
"remote-settings/monitor_changes"and the timestamp is sent with the format of an ETag (eg, surrounded with quotes:"{timestamp}").In Telemetry, we distringuish the different scenariis of synchronization using a
"trigger"field ("manual","startup","broadcast")See Desktop implementation
The text was updated successfully, but these errors were encountered: