Closed OrLevy23 closed 5 years ago
Thx for reporting this.
This is indeed the current behavior, main reason for this is that if a real exception happens we don't want to wait until the to event is sent before the app crashes.
Will think of something to fix this.
As a workaround, if you call captureMessage
from time to time or after captureException
it should flush the queue.
I am closing all old issues, please if this is still a problem feel free to revive it.
Also, consider moving to our new SDK @sentry/react-native
if it still happens there please open a new issue.
I found this problem is still happening in the new SDK, which is only happening on android. react-native: 0.59 @sentry/react-native: 1.3.0
@leedan77 We just tried it and it's not true, it sends it directly.
@HazAT I found that it will delay the error sent just in Emulator, but immediately in real device. That's weird, but thx for your help.
@HazAT This is still a problem for me on @sentry/react-native 1.3.3. I'd like captureException to send immediately if the app hasn't crashed.
OS:
Platform:
Output of
node -v && npm -v && npm ls --prod --depth=0
Config:
I have following issue: We are working on a mobile app with kiosk mode (ipad) and the app does not open and closed regularly, I've encountered with an issue that Sentry.captureException pile the logs and only when we relaunch the app logs are sent.
Expected result: The logs should be sent immediately or once each certain time frame