EyeAuras is a very complex program that continually evolves. Unfortunately, its evolution isn't without setbacks. It has had, currently has, and will likely have errors in the future—some minor and others critical.
This reality is why I've built an entire system allowing users to effortlessly send logs, configurations, screenshots, and any other pertinent data that could aid in diagnosing and rectifying a problem.
Errors fall into 3 main categories:
What's happening?
Something isn't functioning as anticipated; perhaps you've noticed unusual behavior, a trigger that's not working, or an action not executing its intended task. While the app remains operational, it's not running at full capacity.
What should you do?
Click the “Report a problem” button found in the window title. An “Error Report” dialog will pop up, allowing you to share details and send logs.
What's happening?
The application abruptly ceases to function. This is typically due to a critical error within the app or its configuration.
What should you do?
An “Error Report” dialog will automatically display, offering you the chance to send or save logs. After closing the Error Report dialog, the application will terminate since it can't function normally.
What's happening?
The application stops instantly without any alerts or warnings, and without the “Error Report” dialog—it just shuts down.
Several factors could be responsible:
What should you do?
If restarting the app resolves the issue, click “Report a problem” to provide diagnostic data that could help identify the problem—previous logs can still be sent or saved.
If the app consistently crashes upon restart—a rare event—please do the following.
Open the dialog with Report a problem in the window title, or from the reporting button provided by a mini-app. It may also open automatically after an exception.
Describe the problem, select the relevant attachments, then send the report to EyeAuras or save the archive to share with support or a share author. The comment is editable, including when an app prefills it. An empty comment is omitted.
systemInfo.txt and, in current EyeAuras clients, applicationInfo.txt are collected automatically. Application information includes the sender, license features, startup data, tree counts and subscriptions.stacktrace.txt contains exception details when available. Recent application logs and application-window screenshots are selected by default.Read Problem reports and receiving archives for the file format, collected data, an example and instructions for accepting reports as a share author. Older archives without applicationInfo.txt remain usable.
