GITBOOK-316: change request with no subject merged in GitBook

SUMMARY.md

@@ -118,6 +118,7 @@
 * [Frequently Asked Questions](troubleshooting/frequently-asked-questions.md)
 * [Bug Report](troubleshooting/bug-report.md)
 * [Rollback Maestro](troubleshooting/rollback-maestro.md)
+* [Debug Output](troubleshooting/debug-output.md)
 
 ## Community
 

getting-started/build-and-install-your-app/ios.md

@@ -4,7 +4,7 @@
 
 Maestro currently supports iOS Simulator builds (**.app**), AppStore distribution device builds (**.ipa**) are not currently supported. The easiest way to get an app installed on the simulator is by building and running it from Xcode (make sure that simulator target is selected):
 
-<figure><img src="../../.gitbook/assets/Screenshot 2023-02-15 at 13.46.55 (2).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/Screenshot 2023-02-15 at 13.46.55.png" alt=""><figcaption></figcaption></figure>
 
 ## Default build location
 

platform-support/ios-swiftui.md

@@ -10,7 +10,7 @@ In addition to iOS UIKit apps it is possible to write maestro flows for the apps
 
 First lets start with some basic flow for FoodTruck app. Almost every SwiftUI native element is identifiable with maestro studio. For instance here is how the first step of [first\_flow.yaml](https://github.com/artem888/sample-food-truck/blob/main/.mobiledev/first\_flow.yaml) was generated:
 
-<figure><img src="../.gitbook/assets/Screenshot 2023-01-12 at 21.48.45 (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../.gitbook/assets/Screenshot 2023-01-12 at 21.48.45.png" alt=""><figcaption></figcaption></figure>
 
 `index: 0` can be omitted and the first step of the flow looks like that:
 
@@ -82,8 +82,12 @@ Switching between different apps during the same flow is also supported by maest
     id: "breadcrumb"
 ```
 
+<div align="left">
+
 <figure><img src="../.gitbook/assets/Simulator Screen Shot - iPhone 14 - 2023-01-12 at 22.31.14 (2) (1).png" alt=""><figcaption></figcaption></figure>
 
+</div>
+
 breadcrumb is an accessibility id \
 of the “Back to SwiftUI app” \
 button on the screenshot below, which was also found with a help of `maestro studio`

troubleshooting/debug-output.md

@@ -0,0 +1,30 @@
+# Debug Output
+
+### Command Failure Reason
+
+If a command fails, failure reason will be shown in red at the end.
+
+<figure><img src="../.gitbook/assets/231784307-53c51d7f-214f-4eb4-b9ba-9ec34380d280.png" alt=""><figcaption><p>Single Flow Run Failure</p></figcaption></figure>
+
+<figure><img src="../.gitbook/assets/231784391-31aaf0a1-5b80-4372-a1e6-b2e6642af472 (1).png" alt=""><figcaption><p>Multiple Flow Run Failures</p></figcaption></figure>
+
+### Screenshot On Failure
+
+By default, upon failure a screenshot will be generated under the Maestro directory i.e for Mac it's `~/.maestro/tests/<datetime>/`
+
+<figure><img src="../.gitbook/assets/Screenshot 2023-05-18 at 18.54.16.png" alt=""><figcaption></figcaption></figure>
+
+### Maestro Logs
+
+Each flow run will generate:
+
+* A `maestro.log` file that contains Maestro related logs
+* A `commands-*.json` file that contains command metadata.
+
+{% hint style="info" %}
+Device logs are not supported but it's something we plan to add
+{% endhint %}
+
+{% hint style="info" %}
+Such data will be automatically deleted after 7 days
+{% endhint %}