[boehlerlukas]

Version 19.1.0 is in this PR (native pins, version, CHANGELOG with release notes). Merge after iOS + Android 19.1.0 are published (CocoaPods CDN + Maven Central show them), then tag 19.1.0.

What this adds

React Native support for capture requests. Workflows, AI agents and teammates can ask the customer for a screenshot or a screen recording, and can collect the app's logs in the background. The native SDKs do the capturing.

• Gleap.setCaptureEnabled(enabled: boolean): turns in-app screenshots and recordings for capture requests on or off. While off, the widget offers only a file upload. Default on.
• Gleap.setRemoteLogCollectionEnabled(enabled: boolean): turns log collection for capture requests on or off. While off, log requests are answered as unsupported. Default on.
• Both setters check that the native method exists. JavaScript pushed over the air to an older native build does nothing instead of throwing.
• Log flush (Android): the JS network logger pushes to native at most every 500 ms. Before the native SDK collects logs for a request, it asks JS for what it still holds back, via the flushLogs event and logsFlushed(id), and waits at most 500 ms. A destroyed JS context answers right away, and pending flushes are released on invalidate. iOS registers nothing, because the native SDK records the network itself.
• maskView / unmaskView: not exposed. They need a native view.

Verification

• jest 29/29. The new test fails if the flush answers before the hand-over.
• npx bob build OK. tsc is clean apart from an existing error in example/.
• Android javac against the local Android SDK branch is OK on RN 0.66.5 and 0.85.3. Against 19.0.0 it fails only on the new symbols.
• iOS clang syntax check against the local iOS SDK branch is OK. Against origin/main it fails only on the new symbols.

Release

After the native release: bump the iOS podspec dependency and the Android gleap-android-sdk dependency, add the CHANGELOG entry and update the docs version table.

---

The whole program: capture requests ("Show me the issue")

Workflows, AI agents (Kai, Kai Resolve, custom agents) and teammates can now ask a customer for a screenshot (with annotation) or a screen recording in the middle of a conversation, and can collect logs (console, network, custom data, environment data, events) from the customer's app in the background.

One server object, the capture request, backs all three. The customer sees a card in the widget; the SDK in their app does the capture; the result lands in the thread and resumes the workflow or wakes the agent. Background log requests travel over the SDK websocket every SDK already keeps open.

How each platform captures:

• Web, desktop Chrome/Edge: screenshot via one-click "Share this tab" (exact pixels), in-browser render as fallback; recording via tab capture, "Record this page" fallback when sharing is blocked.
• Web, Firefox/Safari/phones/tablets: in-browser screenshot; window/screen recording on desktop, page recording (rrweb) on phones.
• iOS / Android apps (incl. React Native, Flutter, Capacitor): in-app capture of the app's own windows: no OS prompt and no new permissions (no ReplayKit, no MediaProjection). Recordings are H.264 MP4 built from frames.
• Older SDKs, email, WhatsApp & co.: upload / reply-with-attachment fallback, so a request never dead-ends.

Design: https://claude.ai/artifact/5i88BeWfcsWUFhhJmPwK5V (private)

PRs in this program (one per repo):

• Server · Messenger-App · Frontend (dashboard)
• JavaScript-SDK · Gleap-iOS-SDK · Android-SDK
• ReactNative-SDK · Flutter-SDK · Capacitor-SDK (merge after the native release)
• gleap-api-docs (merge after the SDK releases)

🤖 Generated with Claude Code