Roman Zavarnitsyn
Roman Zavarnitsyn
@PaulWoitaschek we've released `3.1.1` which bumps the runtime sdk version to `6.1.0` , so this problem should be gone, but we'll look into a more future-proof solution. Thanks for your...
We'd also need to switch to the new instrumentation API introduced in 7.2 (https://developer.android.com/studio/releases/gradle-plugin-api-updates#instrumentatin-apis-deprecated). For now we'll stick to the deprecated version for compat's sake, but at some point it...
the file is only available for release builds, so either we choose to send this only for release builds or we implement our own dependency gathering logic
what do you mean by "this" exactly? Warning the user? It won't do it, it will just resolve it to the latest, but we could notify the user that we...
no, we want to print a warning to inform the user that *we auto-installed* a new mismatching version of the sentry sdk, because the auto-installation feature is on by default,...
Yea, I think we need to do our best here to make it anonymous/pseudononymous.
Could you share a reproducible example? Because it works on our samples, see here - https://github.com/getsentry/sentry-android-gradle-plugin/blob/40ee9bfc5022ade61640130de38a9c89ad503e57/examples/android-guardsquare-proguard/build.gradle#L52-L54 Have you put this snippet inside the `sentry { }` block?
Closing this with no response for over a month, please feel free to reopen with more details. Thanks!
> wondering how we would do that if the plugin isn't being applied in the first place. Sorry, missing context, do you have an example?