Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect a mismatch in dependency versions #4132

Open
adinauer opened this issue Feb 3, 2025 · 2 comments
Open

Detect a mismatch in dependency versions #4132

adinauer opened this issue Feb 3, 2025 · 2 comments

Comments

@adinauer
Copy link
Member

adinauer commented Feb 3, 2025

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.

@adinauer
Copy link
Member Author

adinauer commented Feb 3, 2025

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.

@adinauer
Copy link
Member Author

adinauer commented Feb 3, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant