mobium logs
This tool on every surface: CLI · MCP · Python · JavaScript · Go · Java · .NET
Read the WebView console, or the device's own log
With no --source it follows the context: in a WebView, what the page has written to its console, including uncaught errors and unhandled promise rejections; on the native shell, the device log — logcat on Android, the unified log on an iOS simulator, and on a real iPhone what the session has captured since it started, since a phone keeps no history.
Each read reports what arrived since the last one. That is what makes "nothing was logged during this step" something you can assert. A console's capture starts when the context is entered; the device log's first read returns the most recent lines. A read narrowed by --app or --level leaves the rest unread.
For why an app died, mobium crashes is the record that survives — the
log is a ring that noise overruns.
Usage
mobium logs [flags]
Flags
| Flag | Type | Default | What it does |
|---|---|---|---|
--app | string | Device log only: one app's lines, by package or bundle id | |
--level | string | Only entries at this level (console: log, info, warn, error, debug; device: verbose, debug, info, warn, error, fatal) | |
--lines | int | 100 | Device log only: the most recent lines to return, at most |
--source | string | Which log: webview or device (default: follow the context) |
And the global flags.
Examples
Read one app's errors from the device log
mobium logs --source device --app com.example.shop --level error
More, from mobium logs --help
mobium logs
mobium logs --level error
mobium logs --source device --app com.example.shop
mobium logs --source device --lines 20
No screenshot: it reads a log, and nothing on the screen changes.
The tool
logs calls app_logs; its arguments and what every client calls it are there.