Crash when screen sharing is enabled and any touch occurs (IndexOutOfBoundsException)

[palmtown]

Description:
When enabling screen sharing, the session starts successfully. However, as soon as the user taps anywhere on the screen (button press or general touch), the app crashes with an IndexOutOfBoundsException.

This seems related to [issue #710](#710), but in my case the crash is reproducible on any touch interaction while screen sharing is active.

Steps to Reproduce:

1. Start an OpenTok session in a React Native app.
2. Enable screen sharing (videoSource: 'screen').
3. Tap on any button or touch anywhere on the screen.
4. App crashes immediately.

Expected Behavior:
The app should continue running while interacting with the UI during screen sharing.

Actual Behavior:
The app crashes with an IndexOutOfBoundsException.

Error Log:
From logcat:

java.lang.IndexOutOfBoundsException: Index 1 out of bounds for length 0
    at jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
    at jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
    at java.util.ArrayList.get(ArrayList.java:434)
    at android.view.ViewGroup.getAndVerifyPreorderedView(ViewGroup.java:4019)
    ...
    at com.opentokreactnative.OTScreenCapturer$1.run(OTScreenCapturer.java:52)
    at android.os.Handler.handleCallback(Handler.java:995)
    at android.os.Handler.dispatchMessage(Handler.java:103)
    at android.os.Looper.loop(Looper.java:363)

Full log excerpt attached from reproduction .

Environment:

• opentok-react-native version: 2.30.2
• React Native version: 0.79.4
• Android version: Android 16
• Device: Samsung S25

Notes:

• The crash only happens when screen sharing is enabled.
• Without screen sharing, UI interactions work fine.
• This may be related to how OTScreenCapturer interacts with the view hierarchy during touches.

[palmtown]

Hello Community,

Note that the sample app doesn't reflect a realistic app structure which doesn't allow you to consistently reproduce. I put together a minimal, reproducible example that mirrors a typical tree where OTSession is wrapped by a context provider and the UI mutates during capture:

Repo: https://github.com/palmtown/opentok-react-native-samples (ScreenSharing sample)

Environment:

• opentok-react-native: 2.30.2
• react-native: 0.79.2
• react: 19.0.0
• Node >= 18 (Yarn 4 in repo)

What’s different vs the simple sample:

• OTSession is wrapped in a context provider.
• A dynamic list mutates every ~1.2s (adds/removes items).
• A Modal overlay appears/disappears every ~2s.
• This causes frequent layout re-ordering while screen capture is active.

Steps to reproduce:

1. Clone the repo and open the ScreenSharing project.
2. In App.js, set your Vonage apiKey, sessionId, and token.
3. Install and run:

npm install
npm run android

4. In the app, tap “Toggle screen sharing” to start screen capture and accept the system prompt.
5. Tap around the screen. Let the dynamic UI and overlay run. It consistently reproduces within ~10 seconds.

Observed crash:

java.lang.IndexOutOfBoundsException: Index 1 out of bounds for length 0
    at jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
    at jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
    at java.util.ArrayList.get(ArrayList.java:434)
    at android.view.ViewGroup.getAndVerifyPreorderedView(ViewGroup.java:4019)
    ...
    at com.opentokreactnative.OTScreenCapturer$1.run(OTScreenCapturer.java:52)
    at android.os.Handler.handleCallback(Handler.java:995)
    at android.os.Handler.dispatchMessage(Handler.java:103)
    at android.os.Looper.loop(Looper.java:363)

Notes:

• If I hide the extra dynamic UI or remove the provider wrapper, the crash is harder to trigger.
• With the provider + dynamic list + transient modal, the crash is reliable shortly after starting screen capture.

This points to a race around view reordering during screen capture in OTScreenCapturer (see line referenced above).

[marinaserranomontes]

Thanks for reporting this! We’re already reviewing it and will keep you updated.

[czoli1976]

@joliveraortega FYI