Markus Hintersteiner
Markus Hintersteiner
The application crashes with StrictMode error after sentry initialization on android api 31, 32, 33.
Hey @AntonVoronkin, thanks for reporting this issue! This is most likely due to our File I/O instrumentation feature, which wraps uses of `FileInputStream`. This also means the root cause is...
The application crashes with StrictMode error after sentry initialization on android api 31, 32, 33.
After some more testing this is happening for me even when the NDK is disabled. sentry sample app ```kotlin StrictMode.setVmPolicy(new StrictMode.VmPolicy.Builder() .detectLeakedClosableObjects() .penaltyLog().penaltyDeath() .build()); SentryAndroid.init( this, options -> { options.setDsn("https://[email protected]/5428559");...
The application crashes with StrictMode error after sentry initialization on android api 31, 32, 33.
Let's try without even packaging the NDK
On Android we always send the full list (of all native loaded `.so` libraries), so there should be no extra effort required. We still need to send the `debug_meta` for...
As the logcat output may contains PII data we need to be careful here. Other considerations: * make the feature opt-in * filter output by running app / process id...
@bruno-garcia up for a PR? 😉
Quoting @romtsn > these would make a perfect hierarchy :smile: -- process fork/start span -- bindApplication span -- first class load span -- class loader created span -- ContentProviders --...
Thanks for reaching out, that's an excellent idea! We'll look into this.
In a first step let's have a manual method, something like `Sentry.setupWebView(webview: WebView)` In a later step we could have automatic code-instrumentation to auto-inject this into every `WebView`.
Ideally we need some handling for this on the backend for obfuscated builds. Let's also make sure we handle basic cases right and e.g. do not mark `com.*` as in-app.