added assets, fixed build errors by updating correct internal links

Author: mrdavidorok

docs/troubleshooting/assets/desktop-app-device-logs.avif

@@ -45,23 +45,23 @@ When you download your project from FlutterFlow and run it locally in your IDE,
 
         Suppose you have a Text widget and added an action that is incomplete. When you try to download the project in such a situation, you might see the following:
 
-        ![Detecting issue -1](imgs/detecting-issue-1.avif)
+        ![Detecting issue -1](../assets/detecting-issue-1.avif)
 
         To track down the error-causing widget in the widget tree, start reading the widget list (from top to bottom in a popup) and locate the widget using its child number. For example, when a widget is displayed as *Child 1*, it will be the first child of its previous widget (see the widget in a popup). And when it is shown as *Child 2,3*, and so on, it will be the sibling widget of *Child 1*.
 
         If you have a practice of naming the widget, it will be straightforward to track it down (as we'll display the exact widget name). Here is how it looks:
 
-        ![Detecting issue -2](imgs/detecting-issue-2.avif)
+        ![Detecting issue -2](../assets/detecting-issue-2.avif)
 
         :::info
-        To find out what caused the widget to fail, you can check errors in the [project issues](../intro/ff-ui/toolbar.md#project-issues).
+        To find out what caused the widget to fail, you can check errors in the [project issues](../../intro/ff-ui/toolbar.md#project-issues).
         :::
 
         **Example 2**
 
         Let's say you have added a custom widget that works fine. But while modifying it, you made some typo in the code, and now it shows this:
         
-        ![Error while building the app](imgs/error-while-building-app.png)
+        ![Error while building the app](../assets/error-while-building-app.png)
         
         The second "**Error:"** line clearly mentions that there is some issue with a method name in a custom code.
 

docs/troubleshooting/assets/detecting-issue-1.avif

@@ -98,11 +98,11 @@ This guide provides a structured approach to troubleshooting and resolving "Run
         If you're using the FlutterFlow Desktop App and running the app with a local run, you can access detailed logs that may point directly to the problem. These logs are especially helpful for catching runtime issues that might not appear in the FlutterFlow UI.
 
         You can learn how to access these logs in this guide:  
-        [Access Device Logs in Local Run](../testing-deployment-publishing/running-your-app/local-run.md#access-device-logs-in-local-run)
+        [Access Device Logs in Local Run](../../testing-deployment-publishing/running-your-app/local-run.md#access-device-logs-in-local-run)
 
         For example, if a user enters a character instead of a numeric value for a quantity field, and that type mismatch causes an error, it will be captured in the logs — allowing you to identify and fix it quickly.
 
-        ![Desktop app's device logs](imgs/desktop-app-device-logs.avif)
+        ![Desktop app's device logs](../assets/desktop-app-device-logs.avif)
 
         :::tip
         Not sure what the error means? Just copy and paste the full error message into ChatGPT and ask for help understanding it.

docs/troubleshooting/assets/detecting-issue-2.avif

@@ -58,7 +58,7 @@ This error is typically triggered when:
 
   We display such errors as *Run mode-only notification* in a snack bar. Here's what it might look like:
 
-  ![Runtime errors](imgs/runtime-errors.avif)
+  ![Runtime errors](../assets/runtime-errors.avif)
 
 Take the steps below to fix this error:
 

docs/troubleshooting/assets/error-while-building-app.png

@@ -109,7 +109,7 @@ Seeing a gray screen in Run Mode usually points to a configuration issue in your
         2. Open the **Debug Info** panel on the left.
         3. Interact with your app and monitor the variables in real time.
 
-        ![null](imgs/null.png)
+        ![null](../assets/null.png)
 
         For instance, if a dropdown variable is unexpectedly `null`, the Debug Info panel can help you trace and correct it. Once fixed, re-test the app to confirm resolution.