Philipp Hofmann
Philipp Hofmann
I think this could answer the time questions https://kandelvijaya.com/2016/10/25/precisiontiminginios/. Also worth looking at this PR https://github.com/getsentry/sentry-cocoa/pull/2105.
@kevinrenskers, could you please play around with the above code to find out how expensive it is to get the current CPU overhead, similar to what we do with slow...
Maybe this library https://github.com/domesticcatsoftware/DCIntrospect can be helpful.
Thanks for opening up this issue @lmmenge. Unfortunately, this isn't an easy fix, and I don't have an ETA for this right now.
Thanks for the input, @lmmenge. We will try to fix this slowly.
@shwetashendage, can you please answer the questions above?
Thanks for reporting this issue, @qinyue. We are aware of this limitation; see https://docs.sentry.io/platforms/apple/guides/ios/performance/instrumentation/automatic-instrumentation/#uiviewcontroller-instrumentation. The reason for this is that checking for all subclasses of UIViewController can be a bit...
We could swizzle classes in binary images matching `SentryOptions.inAppIncludes`. We could also come up with an API to pass in all the UIViewController names.
We could already create overloads right now and deprecate the not Swift-friendly APIs in 8.x.x.
What also would be useful is the available disk space on the device.