Queue timeout before completed restoration

[zgordon02]

• analytics-react-native version:
  ^2.19.2
• Integrations versions (if used):
  N/A
• React Native version:
  0.72.1 AND 0.74.3
• iOS or Android or both?
  BOTH

Steps to reproduce
Send various screen and track events

Here is an example screen event I am sending:
SCREEN event saved {"name": "TEST_SCREEN", "properties": {"_environment": "LOCAL", "_otaVersion": "N/A"}, "type": "screen"}

Expected behavior
No warning
Actual behavior
This warning appears multiple times per session. However, the events are shown properly in the segment console

[zgordon02]

Important to note that I have left almost all options to their default:

    segmentClient.current = createClient({
      writeKey: environment?.segmentKey,
      trackAppLifecycleEvents: true,
    });

[mayfairr]

++ Also getting this.

"@segment/analytics-react-native": "^2.17.0",

[umairmaqbool3]

I am also getting same warnings...

[mcoeur]

Same here with version 2.19.2.
Adding a comment to get notifications on this thread 👌

[seanadkinson]

Also seeing these warnings spewed in my console.

[MarkKravchuk]

Same here, any ideas how to suppress or silence these warnings?

[zgordon02]

Same here, any ideas how to suppress or silence these warnings?

I have not tried this, but the code should be something like this:

import { LogBox } from 'react-native';
// ...
LogBox.ignoreLogs(["An internal error occurred: Error: Queue timeout before completed restoration"]);

That being said, I would not recommend ignoring the warning. Segment should fix it

[leethree]

I think this is caused by this recent change #943

The QueueFlushingPlugin has a default timeout of 500ms and it will fail if it's not intialized within that time. But in our testing it sometimes takes 2 seconds for the entire thing to be ready. So it will block every events from being sent.

[zgordon02]

So it will block every events from being sent.

FWIW I have not noticed events dropped while seeing this warning. It appears to be functioning normally

[anon-r-7]

Also getting this, following.

[CoryWritesCode]

also seeing this after upgrading

[itajenglish]

+1

[DAVIS-PYTH]

Commenting to get updated

[itajenglish]

I think this has been fixed in the last release. I no longer these warnings anymore after updating.

[DAVIS-PYTH]

Thanks @itajenglish

installing version 2.19.4 fixed this for me.

PS: I reached out on LinkedIn

[zgordon02]

Seeing that others have mentioned it's fixed in the latest release, I'm closing this issue.

[dhatGuy]

It might be related. After upgrading to 2.19.4, I keep getting this in the log

INFO Flush triggered but queue restoration and settings loading not complete. Flush will be retried.

[DAVIS-PYTH]

same here with @dhatGuy

[zgordon02]

@dhatGuy I could repoen this issue, but that warning may be unrelated to this one. Can you create a new issue?

[dhatGuy]

@dhatGuy I could repoen this issue, but that warning may be unrelated to this one. Can you create a new issue?

Yes, I have
#989

[anon-r-7]

+1, also getting "Flush triggered but queue restoration and settings loading not complete. Flush will be retried" only after the upgrade.