Skip to content

Blackout: stop() ends it on Android, but on iOS it stays on across stop() and the next launch #143

Closed

Description

@krassx

Found while documenting the 7.x beta (docs PR bugsee/docs#110). Checked against the source on main at 7.0.0-beta3; file:line references are to the SDK repo unless a repo is named. Not reproduced on a device unless a line says so.

On Android stop() ends a blackout. On iOS (7.0.0-beta7) only endBlackout() ends it, so a blackout begun before stop() is still on after the next launch(): recordings stay black until the app calls endBlackout().

Suggested direction

Make the platforms consistent (end it on stop() on both, as the cross-SDK spec says: "blackout lasts until endBlackout() or stop()"), and cover it with an e2e on iOS.

Activity

  1. krassx commented on Oct 20, 2026

    @krassx
    ContributorAuthor

    The fix belongs to the underlying SDK, not React Native one.

  2. krassx commented on Oct 21, 2026

    @krassx
    ContributorAuthor

    Follow-up from PR #153: add an iOS e2e case in examples/bare/e2e/blackout.test.ts (launch, startBlackout, stop, launch, assert isBlackout false and a BlackoutEnded event). Also decide relaunch() semantics across platforms, and ideally fix stop() in the iOS SDK so the wrapper TODO(#143) can go.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions