sentry-cocoa: Crashes reported on iOS Prod build
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
we have integrated Sentry in our App named 99acres to trace crashes and other data as well . It impacted our crash free users so with immediate effect we decided to remove from production let me share steps which I use to implement
Native IOS In pod file: pod ‘Sentry’, :git => ‘https://github.com/getsentry/sentry-cocoa.git’, :tag => ‘8.5.0’
App Delegate file
In AppDelegate file a private func is defined which is getting called from did finish launching method , lets have a look on code snippet:
private func traceSentry(){
SentrySDK.start { options in
options.dsn = "https://a7186974bca04563ad73b5c4edb5c5e5@o1118757.ingest.sentry.io/4505006327791616"
// We recommend adjusting this value in production
options.debug = true
options.tracesSampleRate = 1.0
options.profilesSampleRate = 1.0
options.appHangTimeoutInterval = 1
options.enableSwizzling = true
options.enablePreWarmedAppStartTracing = true
options.attachScreenshot = true
options.attachViewHierarchy = true
if #available(iOS 15.0, *) {
options.enableMetricKit = true
} else {
// Fallback on earlier versions
}
}
let error = NSError(domain: "com.99acres.com", code: 1, userInfo: nil)
SentrySDK.capture(error: error)
}
React Native Side
in Package.json -> “@sentry/react-native”: “^5.3.1”
while in App.js
import * as Sentry from "@sentry/react-native";
Sentry.init({
dsn: "https://96557d741b4d40cebaa7c03a6ddaf527@o1118757.ingest.sentry.io/6152887",
autoInitializeNativeSdk:false,
enableNative:false,
});
Expected Result
It should be Crash free , please do suggest if any thing goes wrong
Actual Result
Product Area
Performance
Link
No response
DSN
https://a7186974bca04563ad73b5c4edb5c5e5@o1118757.ingest.sentry.io/4505006327791616
Version
8.5.0
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 28 (17 by maintainers)
I think that’s going to be a relatively small proportion of the overall amount of crashes. The screenshot shows a total of 210 crashes, but #2995 only addresses the ones from
SentryProfiler.processBacktrace, which is only 5% of the total. We would really need a stacktrace to see what’s up with+ [SentryProfiler isRunning]. I’m not sure what’s up with the most prevalent crash in the serializer. Stack traces will definitely be helpful.