You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could use io.sentry.BuildConfig.VERSION_NAME as a target and compare each integrations own version, e.g. io.sentry.android.core.BuildConfig.VERSION_NAME against it then make that integration noop on a mismatch.
Consider proguard/r8 here, maybe fallback to just letting the SDK work normally if we can't detect the BuildConfig files and in a follow up major we change this to be required for the SDK to work.
Problem Statement
Sometimes customers end up with a mix of versions in different Sentry dependencies.
Solution Brainstorm
We could detect versions, compare them and NoOp if there's a mismatch on init. Same can be done for our
sentry-opentelemetry-agent
.The text was updated successfully, but these errors were encountered: