[romtsn]

📜 Description

Fixes the flaky CapturedResponseBodyTest > reports once when the body is closed while another thread is reading it.

The test signaled "the reader is reading" right after the reader got the first chunk, before the reader entered the next read(). When wrapper.close() landed in that gap, it closed the inner BufferedSource first. The reader's next read() then threw Okio's IllegalStateException("closed"), the reader thread died, and readDone never counted down:

Exception in thread "Thread-3" java.lang.IllegalStateException: closed
java.lang.AssertionError: the reader must finish once the body is closed

ParkingSource now counts down a parked latch right before it blocks, and the test waits for that instead. close() then always lands while the reader is blocked inside read(), which is the situation the test is about. With a 300 ms sleep in the old gap the test failed every time before this change and passes with it.

Test-only change, no SDK code touched.

💡 Motivation and Context

The test failed in 4 of the last 6 failed Build runs on unrelated branches this week.

💚 How did you test it?

Reproduced locally with a widened gap, verified the fix under the same gap, then ran the class 3 times without it.

📝 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

#skip-changelog

🤖 Generated with Claude Code

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings