reverted the changes. renamed troubleshooting guide to detecting issues

Author: mrdavidorok

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

@@ -31,42 +31,5 @@ When you download your project from FlutterFlow and run it locally in your IDE,
 
     If the current version on your machine is different than what is currently supported by FlutterFlow, you can downgrade or upgrade to the supported version. You can learn more about [**upgrading Flutter**](/testing/local-run/#4-running-app-on-device). ​By following these steps, you can fix the errors that you face after downloading the code and run locally. 
 
-## Resolving In-App Errors Before Downloading
-
-    Sometimes, errors in your app — such as misconfigured widgets or faulty custom code — can cause download or build failures. FlutterFlow displays helpful error popups to help you catch and fix these issues before downloading your code.
-
-    - **Error popup**
-    
-        If you see a popup, open the red-colored section (click *Read More*), and at the bottom, you will see the exact widget or error causing the build or download failure.
-    
-        Let's see a couple of examples of what you might encounter while building your app:
-    
-        **Example 1**
-    
-        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](../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](../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).
-        :::
-    
-        **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](../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.
-
-If you continue to experience issues, contact the FlutterFlow support team via live chat or email at [email protected].
-
-
-
 
+If you continue to experience issues, contact the FlutterFlow support team via live chat or email at [email protected].

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

@@ -92,29 +92,12 @@ This guide provides a structured approach to troubleshooting and resolving "Run
 - **Utilize local debugging**: 
 
     If the error is elusive, running the debugger locally on your downloaded code can help identify the issue.
-
-    **Use Device Logs in the FlutterFlow Desktop App**
-
-        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)
-
-        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](../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.
-        :::
-
-        In fact, for the error shown above, **[we asked ChatGPT](https://chat.openai.com/share/77f3ceb5-6b2f-4f94-b85c-e01a1fce002a)** to explain and resolve the issue — and the solution turned out to be quick and simple.
-
+    
 - **Leverage browser tools**: 
 
     The browser's console and developer tools can offer insights, especially when dealing with errors that don't manifest in traditional debug outputs.
 
 
 :::info[Additional Resources]
 [Basic Troubleshooting Guide – FlutterFlow Documentation](https://docs.flutterflow.io/troubleshooting/basic-troubleshooting-guide)
-:::
+:::

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

@@ -1,17 +1,15 @@
 ---
 slug: /troubleshooting
-title: Troubleshooting Guide
+title: Detecting Issues
 description: A guide to troubleshoot or debug issues that occur within FlutterFlow project.
 tags: [Troubleshooting]
 sidebar_position: 0
 keywords: [Troubleshooting, Debugging, Detect Issues, Runtime Errors]
 ---
 
-# Troubleshooting Guide
+# Detecting Issues
 
-This is a general troubleshooting guide for any issues that occur within FlutterFlow projects.
-
-## Detecting issues
+This is a general troubleshooting guide for detecting any issues that occur within FlutterFlow projects.
 
 We've improved our issue detection capabilities and added features to provide clearer insights into what might be causing these problems. Here are some options you can use to troubleshoot the issue.
 

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

@@ -25,9 +25,9 @@ This error is typically triggered when:
 
   Example:
 
-  - If Firestore rules are configured as:
+  - If Firestore rules are configured as:  
 
-    ```js
+  ```js
     rules_version = '2';
     service cloud.firestore {
       match /databases/{database}/documents {
@@ -37,29 +37,18 @@ This error is typically triggered when:
       }
     }
     ```
-
+    
     Any Firestore query will fail because no read or write access is allowed.
 
   - If rules allow only authenticated access:
 
-      ```js
+    ```js
       allow read, write: if request.auth != null;
-      ```
-
+    ```
     And a query is placed on a page before the user signs in (e.g., on the login screen), it will trigger this error.
 
     Descriptive widget names can help you quickly identify which query or widget is triggering the permission issue. In the example above, the error message references a widget named Container. Renaming it to something like UserQueryContainer can make debugging easier.
 
-**Runtime errors (Run mode-only notification)**
-
-  Runtime errors in app development are errors that occur during the execution of the app. Unlike the errors that we display while you build the app, runtime errors occur while the app is running.
-
-  For instance, if Firestore security rules aren't properly configured, the app might run into permission issues at runtime, leading to failures in data retrieval or display. This kind of error might not be evident during app building but becomes apparent only when the app interacts with the Firestore database during actual operation.
-
-  We display such errors as *Run mode-only notification* in a snack bar. Here's what it might look like:
-
-  ![Runtime errors](../assets/runtime-errors.avif)
-
 Take the steps below to fix this error:
 
   - **Review Firestore Rules**