Closed cvvspb closed 4 years ago
Hi @cvvspb
Could you confirm are you using a debugger? You should see something in the logs like this if you are :
WARN : BSG_KSCrashSentry.c (103): BSG_KSCrashType bsg_kscrashsentry_installWithContext(BSG_KSCrash_SentryContext , BSG_KSCrashType, void ()(void *)): KSCrash: App is running in a debugger. Only user reported events will be handled.
If you are, only handled exceptions will be sent which might explain the behaviour you are seeing.
According to a post here the WebKit errors suggest there may be intermittent network connection issues which could also explain why the reports are not sent. Is this something that could be happening while your application is running?
Closing out due to inactivity. Any further related comments to add, please do drop them in here and we'll re-open the issue.
Description
Issue
Crash logs are generated but not sent.
Environment
Library versions:
cocoapods version (if any) (
pod -v
): 1.8.4iOS/Android version(s): 13.5.1
simulator/emulator or physical device?: physical device
debug mode or production?: production
[x] (iOS only)
[BugsnagReactNative start]
is present in theapplication:didFinishLaunchingWithOptions:
method in yourAppDelegate
class?[ ] (Android only)
BugsnagReactNative.start(this)
is present in theonCreate
method of yourMainApplication
class?Example Repo
yarn install
andreact-native run-ios
/react-native run-android
Example code snippet
So, Bugsnag says it's sending the reports, but I can't see them. Android is reporting just fine.
Don't know if it has anything to do with those com.apple.WebKit notifications (I'm not using the WebView, maybe GoogleMaps does) or tcp_input messages.