One-click error reports

If a task ends with an error, Lusiesta helps you report the problem with a single button - the diagnostics that matter are attached to your ticket automatically. You do not have to collect anything by hand, take screenshots or dig into technical details. Below is what exactly reaches support, how to send a report manually and how to speed up the investigation.

What happens automatically

When a task fails, the app captures diagnostics before it closes the task - that is, while the phone is still standing on that very “broken” screen. This is the key point: a minute later the phone has turned its display off or gone back to the home screen, and it tells you nothing at all.

The captured archive is attached to the task straight away and uploaded to the server in the background. So the basic case looks like this: a task fails and the developer already sees which step and which screen it happened on. The upload is gentle and runs in the background: if there is no internet at that moment, the app will not complain and will not disrupt the farm.

What is inside a report

• screenshot.png - a screenshot of the phone at the moment of the failure;
• dump.xml - the interface tree of that same screen: it shows which button was not found;
• log.txt - the task execution log;
• task.json - the task parameters with secrets stripped out (proxy passwords and the like never reach the report);
• comment.txt - your comment, if you added one.

The actual set of attachments is visible right in the send dialog: the “Attachments” block lists the files with their sizes. If it is empty and reads “No diagnostics captured (no bundle for this task)”, there is no archive for this task - for example, because the task was stopped by hand rather than failing.

How to send a report manually

1. Open the “Tasks” page and turn on the “Errors” filter - only failed tasks remain.
2. Find the row you need: use the “Device”, “Time” and “Result” columns - the result spells out the reason for the error.
3. Click “Report an error” in the task actions.
4. Check the “Attachments” block - they are attached on their own, there is nothing to pick separately.
5. Write a comment in the “Describe what happened” field (up to 1000 characters) and click “Report an error”.
6. Wait for the app to answer: it either confirms that the report was sent or says “Could not send (check your internet connection and sign-in)”.

If you get the second message, check your internet connection and that you are signed in, then send it again. The report is not going anywhere, it is stored on disk. You can also send it later: the button stays available as long as the task is visible in the list.

What to write in the comment

The screenshot and the log answer the question “what was on the screen”, but not “what did you expect”. Three lines from you save a day of back and forth. There is no need to write technical details - they are already in the archive, which shows the phone model, the Android version and the scenario step where everything stalled:

• what you were running (publishing to TikTok through a clone, for example);
• what you expected to see and what you got instead;
• whether it repeats on other phones or only on this one.

Do not delete a failed task before you send the report: the link to the diagnostics archive disappears from the list along with it. Report first, tidy up afterwards.

How long reports are kept

Archives live in the app’s data folder and are deleted automatically after 14 days - otherwise screenshots of logged-in screens would pile up forever. If a problem shows up rarely, do not put the report off for a month: by then the archive will be gone.

Next to the send button there is “Copy ID” - the task identifier, something like T-0042. Quote it when you write to support and the report is found instantly.

Failures outside the task list

Some operations bypass the task dispatcher, yet diagnostics are still collected for them. A failed proxy setup from the “Proxies” page also captures an archive with a screenshot and a log and sends it - nothing extra is needed from you. Clone installation errors are sent together with the device fingerprint (model, Android version).

Preview is a story of its own: if the picture does not come up, the app sends a short summary for each problem phone by itself, and there is no need to create an error report for that. What to do in such cases is described in No phone preview.

If a task does not fail but behaves oddly

Sometimes everything is formally “Completed”, yet the actual result is wrong. In that case there will be no error report and you need a different route:

1. open the “Logs” page, filter by device and click “Export” - you get a text file;
2. go to the “Support” page and open a ticket;
3. attach the file with “Attach” (up to 5 files, up to 20 MB each) and describe what went wrong.

How tasks and their statuses work is covered in Creating and running tasks: it also explains how “Error” differs from “Stopped” and why tasks do not survive an app restart.