Open sregg opened 11 months ago
I tried this custom flush policy but I'm still not seeing the Application Backgrounded
until re-opening the app.
class FlushAppBackgroundedPolicy extends FlushPolicyBase {
start() {
// no-op
}
onEvent(event: SegmentEvent): void {
if ('event' in event && event.event === 'Application Backgrounded') {
console.log({ event }); // is logged properly on background
this.shouldFlush.value = true;
}
}
end(): void {
// no-op
}
}
@sregg Thanks for the report! Is this happening in iOS or Android (or both) ?
@sregg Thanks for the report! Is this happening in iOS or Android (or both) ?
I've only tried on iOS. I'll try Android tomorrow.
It's also happening on Android.
@sregg I'm wondering about this too. we upgraded from 1.5.2 to 2.10.1 a while back and have noticed a significant increase in delta between event and event_received. i can't seem to find any information about what default flush behavior is for startup and background events. should it be flushing by default in those cases or do you need to set BackgroundFlushPolicy
explicitly for that to happen?
To flush on background you have to add the background policy explicitly I think. That seems to flush all events except the background event itself.
Any update on this from the Segment team?
Steps to reproduce
BackgroundFlushPolicy
to client flush policies (e.g.segmentClient.addFlushPolicy(new BackgroundFlushPolicy());
Expected behavior
Application Backgrounded
event is also visible in Segment's debuggerActual behavior
Application Backgrounded
event is only visible after you re-open the app