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

Fix 2.x SDK interop #3036

Merged
merged 2 commits into from
May 2, 2023
Merged

Fix 2.x SDK interop #3036

merged 2 commits into from
May 2, 2023

Conversation

trask
Copy link
Member

@trask trask commented May 1, 2023

Found this while testing locally. Prior to 3.4.0 the 2.x integration didn't require iKey to be configured on the 2.x side (only on the 3.x side). This broke in 3.4.0, and currently the 2.x integration doesn't emit any telemetry if there's no iKey configured on the 2.x side.

mv.visitMethodInsn(
INVOKEVIRTUAL,
unshadedPrefix + "/TelemetryConfiguration",
"isTrackingDisabled",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't find any tests for isTackingDisabled or isDisabled. How does customers use it? no ikey is only when they disable tracking, correct?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they don't use it directly, the 2.x TelemetryClient calls isDisabled() is called in several places

@trask trask merged commit 3792327 into main May 2, 2023
@trask trask deleted the fix-2x-integration branch May 2, 2023 16:25
@trask trask changed the title Fix 2.x integration Fix 2.x SDK interop May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants