> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/guides/developer-guide/flutter-mobile-app-ui-developer-guide/troubleshooting.md). # Troubleshooting Handling common issues and errors * **Dependency Conflicts**: Check for conflicting versions of dependencies in your `pubspec.yaml` file and resolve them by specifying compatible versions. * **Missing or Incorrect Imports**: Verify that all necessary packages are imported correctly. Check for typos or missing package names. * **Widget Rendering Issues**: Debug issues related to widget rendering by checking the widget tree, examining layout constraints, or identifying invalid or conflicting widget properties. ### Debugging Techniques * **Logging**: Use print statements or logging libraries like `logger` or `flutter_logger` to log important information during development. * **Debugging Tools**: Utilize Flutter's debugging tools such as the Flutter DevTools, which provide insights into the app's performance, UI layout, and network requests. Use breakpoints to pause execution at specific lines of code for closer inspection. ### Error Handling Strategies * **Try-Catch Statements**: Surround code that may throw exceptions with a try-catch block to handle anticipated errors gracefully. Use the catch block to provide appropriate error messages or perform recovery actions. * **Null Safety**: Embrace Flutter's null safety feature to catch and handle null-related errors at compile time. Use the `?` and `!` operators to handle nullable variables and avoid null-related runtime errors. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digit.org/platform/guides/developer-guide/flutter-mobile-app-ui-developer-guide/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.