Closed efstathiosntonas closed 3 days ago
It appears that this is happening only on 2.19.2, downgrading to 2.19.1 does not throw the rejection any more.
It may be unrelated, but I was getting the same error mentioned in the OP and also: Queue timeout before completed restoration
. Downgrading to 2.19.1 resolved both of them.
hi folks thanks for the report- will prioritize this and follow up asap.
@efstathiosntonas @gitwilliam At present, the only PR I can find related to this issue is #943. From what I can tell in my investigation so far, these errors on app launch are expected and described in detail in that PR mentioned above. The change was introduced to prevent flushing before plugins (including SegmentDestination) are initialized. I can reproduce the warnings you are seeing but I am not experiencing any event loss.
Please let me know if you are experiencing event loss or any other unintended/regressive behavior and we can go from there.
@alanjcharles No event loss, but I'm getting these errors every few seconds when running my app (not just at app launch). Please have them as opt-in through a config flag or something, it's clogging up my debug terminal!
@alanjcharles same as @jvgeee, It’s clogging the terminal and it’s really annoying since our minds automatically tries to find out what is going on when we see a promise rejection happening 😂
I have same problems. any solutions?
We also have that here.
Same here.
getting same error on 2.19.1 with sdk "expo": "50.0.19"
same warning on 2.19.1
Addressed in #966
Addressed in #966
Getting this still
I get this on app start:
and later on:
https://github.com/segmentio/analytics-react-native/blob/e079c71958d8f57cdc7bf4f1131bd2ce4d483284/packages/core/src/util.ts#L236
analytics-react-native
version: 2.19.2Integrations versions (if used):
React Native version: 0.74.2
iOS or Android or both? Both
Steps to reproduce
Expected behavior don't know Actual behavior throws promise timeout