Console and logs

By the end of this page you will be able to find, in a few seconds, the line that explains why a script failed. ⏱ 5 minutes

Get to know the screen

Click Console in the sidebar. The screen has two parts: Sources on the left, the log on the right.

1234567891011

• Sources (marks 1 to 3): All sources, App (messages from AppsMobs), Scheduler (scheduled tasks), then one entry per device or script. The small number on the right counts lines.
• Levels (mark 5): Errors, Warnings, Success, Info, Debug, each with its counter.
• The icons right of the search bar (marks 6 to 11) are the tools.

Find an error

1. 1

   Open the Console

   Click Console. If a script is running, its output shows live. If there is nothing, you read "Nothing logged yet": run a script, its lines will appear here.

2. 2

   Pick the source

   On the left, click the device or script you care about (for example your phone's serial number). The title above the log changes and only its lines remain. For AppsMobs' own messages only, click App; for scheduled tasks, Scheduler.

   Clicking the icon on the right of a device opens its panel.

3. 3

   Isolate a level

   Above the log, click Errors: only error lines remain. Ctrl + click another level (for example Warnings) to combine them.

   You are done when the log shows only the chosen levels. If nothing shows: "No line matches these filters". Change the source, levels or search.

   

4. 4

   Search a word

   Click Search the log (Ctrl+F) or press Ctrl + F, then type a word (for example timeout). The counter reads "N shown · M recorded".

5. 5

   Freeze the screen to read in peace

   If the log scrolls too fast, click Pause display (mark 7). The message "Display paused, lines are still recorded" confirms it: nothing is lost. Click again to resume; Follow new lines (mark 6) sticks the view to the bottom. Wrap long lines (next to it) breaks long lines onto the next row.

6. 6

   Copy or export

   Copy visible lines puts the visible lines on the clipboard ("Visible lines copied"). Export saves the current view to a file; the app tells you where. Only the displayed (so filtered) lines are copied or exported.

Answer a script that asks a question

A script that calls input("question") stops and waits. The Console then shows "Waiting for your answer" with the question. Type your answer in the field ("Type the answer, then Enter") and press Enter or Send. Later leaves the question pending; if several scripts wait, a "+N waiting" note says so. A badge on the Console sidebar entry warns you.

The full log of a script

The Console is a preview: it keeps a limited number of lines in memory (6,000) and the oldest ones leave the view. To keep everything a script wrote, unfiltered, AppsMobs can write one file per run:

• The folder-shaped button opens the Full run logs folder.
• The settings (turn on, number of logs kept, maximum size, Delete all) are in Settings, Logs tab: see Settings.
• If you see "No log file for this run. Turn on run logs in Settings > Logs.", that option was off when the script started.

It does not work?

What next

• Troubleshooting: error messages sorted by theme.
• Settings: tune run logs.
• Scheduling with Automation.