User GuideUser Guide · Platform

Mobile App

Getting around

The native app for iPhone/iPad and Android phones/tablets covers every core feature in this guide, plus a few things unique to a phone in your hand: pull-to-refresh on your ticket, project, and notification lists, and the same filters (project, status, priority, issue type, assignee, tags) on the ticket list.

Screen recording

Record your device’s screen right from inside the app, with optional microphone audio, and attach it directly to a ticket — no separate screen-recorder app, no exporting or re-uploading a video from your camera roll.

Attachments and dictation

Attach photos and videos straight from your device’s photo library, or any file type through the document picker. When writing a description or comment, dictate it instead of typing — speech-to-text runs in real time, on-device.

Notifications

Native push notifications keep you on top of ticket activity.

Recording a bug in your own app

The Mobile app can pair with a separate, third-party app that has the Logtryl SDK (React Native or Flutter) built into it, and then remotely control a live debug recording on that app — useful when you’re testing your own product and want to capture exactly what happened, technically, while reproducing a bug.

Pairing a device

From Settings in the Mobile app, generate a short code. Enter that code inside the third-party app — either through the SDK’s ready-made pairing drawer widget, or however the developer of that app chose to expose it with a few lines of code. It’s a copy/paste code, not a QR scan.

Starting and stopping a recording

From the Create Ticket screen, starting an SDK debug recording remotely tells the paired app to start capturing its own console output, network requests (headers and bodies included), and unhandled exceptions, and best-effort switches you to that app so you can reproduce the bug. Stopping the recording — or simply backgrounding the Mobile app — uploads the captured session, which is linked to the ticket automatically whether the upload finishes before or after the ticket itself is saved.

If the other app crashes mid-recording
Exceptions captured up to the moment of the crash are still recovered and uploaded the next time that app launches. Console output and network requests captured before the crash are not recoverable — they only exist in memory until upload, and a crash doesn’t give them a chance to be saved.

Reviewing a recorded session

SDK-recorded sessions appear read-only in the ticket’s Debug tab on both Desktop and the Web Dashboard, right alongside any Desktop-recorded sessions, clearly labeled as a mobile/SDK session. Every session records which platform (iOS or Android) captured it, and — if the developer supplied them when setting up the SDK — the host app’s own version and device model, so you’re looking at real device details rather than a generic label.

Counts toward your plan's debug-session limit
SDK-recorded sessions count toward the same monthly debug-session cap as Desktop-recorded ones — recording from a paired device instead of Desktop doesn’t give you extra headroom.