BackgroundFlushPolicy doesn't flush the Application Backgrounded event

[sregg]

    "@segment/analytics-react-native": "2.15.0",
    "@segment/analytics-react-native-plugin-braze": "^0.5.4",
    "@segment/analytics-react-native-plugin-mixpanel": "0.3.3",
    "@segment/sovran-react-native": "1.0.4",

Steps to reproduce

1. Add BackgroundFlushPolicy to client flush policies (e.g. segmentClient.addFlushPolicy(new BackgroundFlushPolicy());
2. Open the app
3. Trigger an event
4. Close the app

Expected behavior

• The event should be visible in Segment's debugger
• The Application Backgrounded event is also visible in Segment's debugger

Actual behavior

• The event should be visible in Segment's debugger
• The Application Backgrounded event is only visible after you re-open the app

[sregg]

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
  }
}

[oscb]

@sregg Thanks for the report! Is this happening in iOS or Android (or both) ?

[sregg]

@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.

[sregg]

It's also happening on Android.

[ekallevig]

@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?

[sregg]

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.

[sregg]

Any update on this from the Segment team?

[alanjcharles]

Hi @sregg @ekallevig complete apologies here- we have had some turnover in the last year and this simply got lost in the shuffle. I wish I had a better excuse for you.

It seems Oscar had plans to address this but I am not sure he got to it. If this is still an issue would it be possible for you to reach out to [email protected] with a copy of this report? The support engineering team will be able to prioritize this and escalate a fix to us over the course of the next sprint. I will tell their mobile technical product lead to look out for your email so he can be sure to follow up and resolve this as soon as possible.

Apologies again for the delays. Looking forward to resolving this.