analytics-react-native icon indicating copy to clipboard operation
analytics-react-native copied to clipboard

Error: Promise timed out

Open lucasoliveiraw00 opened this issue 1 year ago • 5 comments

I'm facing a "Promise timed out" error in my application. Is anyone else having this issue?

Captura de Tela 2024-08-01 às 21 22 52 Captura de Tela 2024-08-01 às 21 29 34

  • analytics-react-native version: 2.19.2
  • Integrations versions (if used):
  • React Native version: 0.73.8
  • iOS or Android or both? Android

lucasoliveiraw00 avatar Aug 02 '24 00:08 lucasoliveiraw00

I'm facing a "Promise timed out" error in my application. Is anyone else having this issue?

Captura de Tela 2024-08-01 às 21 22 52 Captura de Tela 2024-08-01 às 21 29 34

  • analytics-react-native version: 2.19.2
  • Integrations versions (if used):
  • React Native version: 0.73.8
  • iOS or Android or both? Android

I am also having this issue!

analytics-react-native version: 2.19.2 Integrations versions (if used): React Native version: 0.73.6 iOS or Android or both? both

kip-west avatar Aug 06 '24 20:08 kip-west

Same for me.

bit-scrambler avatar Aug 08 '24 06:08 bit-scrambler

Duplicate of: https://github.com/segmentio/analytics-react-native/issues/954 which shouldn't be closed.

This issue is around for 2 months and no one from segment team cares to fix. 👎

efstathiosntonas avatar Aug 13 '24 15:08 efstathiosntonas

I am having the issue too. Any updates?

amkiran avatar Aug 22 '24 15:08 amkiran

@efstathiosntonas @amkiran @bit-scrambler @kip-west @lucasoliveiraw00 apologies for the inconvenience and delay here, folks. To be honest, we have had some unexpected turnover recently and are working to re-align as quickly as possible.

The original purpose for adding this error was to actually surface initialization issues for customers and help ensure events created before initialization were successfully sent to Segment when they would be expected to be sent. The unintended consequence has been a noisy debugging experience for a lot of folks. For that we do apologize, however the original goal was to provide better logging/reporting and is not the result of a regression to the SDK. Here is the original PR with this change for your reference.

I have just merged a PR that should make this error a lot less noisy while still providing its intended value. I am not seeing any warnings or logs in my latest build but please let me know if that is not the case for you and we can go from there. I will publish a release first thing next Monday. Thanks again for your patience here.

image

alanjcharles avatar Sep 12 '24 18:09 alanjcharles

@alanjcharles I've updated Segment to all the latest as possible an unfortunately I'm still receiving the promise timeout issue. Looks like to be on the utils file and I found it is only called on the QueueFlushingPlugin. To me it is happening all the time.

I have: "@segment/analytics-react-native": "^2.19.5", "@segment/sovran-react-native": "^1.1.2",

React Native: 0.73.1

And this is my Sentry log. I'm now muting this error from Sentry because it is too noisy.

Captura de pantalla 2024-10-07 a la(s) 2 42 58 p  m

Oh one more thing, this is happening to me in both iOS and Android.

smfunder avatar Oct 07 '24 17:10 smfunder

@alanjcharles hello, is this issue solved, or just marked completed? It consumes our error quote quite significantly.

fehergeri13 avatar Apr 11 '25 08:04 fehergeri13