Fixed potential crash and hang in ScreenCaptureConnection

[adrian-niculescu]

Summary

• Fixed crash when resuming canceled continuations by adding invokeOnCancellation cleanup
• Added defensive check for bindService() failure

Problem

Crash on cancellation (main issue): If a coroutine waiting in queuedConnects is canceled (e.g., user navigates away, timeout), the continuation remains in the set. When handleConnect() later calls resume() on the canceled continuation, it throws IllegalStateException.

Infinite hang (defensive): The bindService() return value was ignored. While the service is declared in the SDK manifest and this is unlikely to fail in practice, if it ever does, the coroutine would suspend indefinitely with no indication of what went wrong.

Solution

• Add invokeOnCancellation handler to remove the continuation from queuedConnects when the coroutine is canceled
• Check bindService() return value and throw immediately with a descriptive error if binding fails

[changeset-bot]

🦋 Changeset detected

Latest commit: 6a755be

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
client-sdk-android	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[davidliu]

LGTM!