Skip to content

fix(okhttp): keep the wrapped EventListener per Call - #6003

Open
markushi wants to merge 7 commits into
mainfrom
fix/okhttp-event-listener-per-call
Open

fix(okhttp): keep the wrapped EventListener per Call#6003
markushi wants to merge 7 commits into
mainfrom
fix/okhttp-event-listener-per-call

Conversation

@markushi

Copy link
Copy Markdown
Member

📜 Description

SentryOkHttpEventListener held the wrapped EventListener in a single mutable field that
callStart overwrote for each call. It is now kept in a per-Call map, the same pattern the class
already uses for eventMap. No public API change.

💡 Motivation and Context

OkHttp uses one listener instance for all calls, thus concurrent calls were all delegated to the
listener made for the call that started last. This breaks the EventListener.Factory contract and
loses the terminal callEnd/callFailed of every overlapping call.

💚 How did you test it?

Added unit tests.

📝 Checklist

  • I added GH Issue ID & Linear ID
  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.
  • Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@linear-code

linear-code Bot commented Aug 26, 2026

Copy link
Copy Markdown

JAVA-695

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@sentry

sentry Bot commented Aug 26, 2026

Copy link
Copy Markdown

📲 Install Builds

Android

🔗 App Name App ID Version Configuration
SDK Size io.sentry.tests.size 8.54.0 (1) release

⚙️ sentry-android Build Distribution Settings

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@markushi markushi added the sanity-check PR needs a lightweight review for obvious issues label Aug 26, 2026
@markushi
markushi marked this pull request as ready for review August 26, 2026 10:00
Move the okhttp changelog entry into a new Unreleased section, as
8.54.0 was released on main.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

@0xadam-brown 0xadam-brown left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks for this 💯 !

One comment worth addressing; otherwise looking good.

Comment thread sentry-okhttp/src/main/java/io/sentry/okhttp/SentryOkHttpEventListener.kt Outdated
Keep both Unreleased changelog entries.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@markushi
markushi force-pushed the fix/okhttp-event-listener-per-call branch from bb23afd to b508070 Compare August 28, 2026 06:58
@markushi
markushi requested a review from 0xadam-brown August 28, 2026 07:10

@0xadam-brown 0xadam-brown left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Excellent! One tweak more to satisfy the EventListener.Factory contract, and I think we'll be there 🥇

// callEnd()/callFailed(), so there is not always a listener bound to the call. Create one on
// the fly in that case, but do not put it in the map: nothing would remove it again, because
// a call that is canceled before it starts never gets a callEnd() or callFailed().
val originalEventListener =

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We're close! (and thanks for the great updates)

We still need to preserve the contract of EventListener.Factory that ensures only one EventListener instance is produced per Call lifecycle. Ie, the listener returned by the factory for a given call needs to be the listener that captures i) all of that call's lifecycle and ii) no other call's lifecycle.

We've fixed (ii), but we're still violating (i) in the case of cancelation because we're creating an extra listener for early and late cancel() invocations.

Possible solution

Thoughts about using a weak per-call map for the wrapped listener instead? Something like a WeakHashMap<Call, EventListener> guarded by synchronized, with a getOrCreateOriginalEventListener(call) helper used by both callStart and canceled().

That'd^^ let us avoid removing entries on callEnd / callFailed, and completed calls would be gc'd as soon as the Call instance is unreachable.

}

@Test
fun `cancel before callStart is delegated`() {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks for the new tests 💯

Bonus points if our cancellation tests can assert the stronger factory-contract invariant 👍

(Right now cancel before callStart is delegated and cancel after callEnd is delegated prove that some listener receives canceled(), rather than that a single listener receives all lifecycle callbacks.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sanity-check PR needs a lightweight review for obvious issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SentryOkHttpEventListener breaks EventListener.Factory contract

2 participants