Datasets:
Ekhlass
/
flutter_docs

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
1
372
in addition, the resume button continues regular
execution of the application.
<topic_end>
<topic_start>
console output
console output for the running app (stdout and stderr) is
displayed in the console, below the source code area.
you can also see the output in the logging view.
<topic_end>
<topic_start>
breaking on exceptions
to adjust the stop-on-exceptions behavior, toggle the
ignore dropdown at the top of the debugger view.
breaking on unhandled excepts only pauses execution if the
breakpoint is considered uncaught by the application code.
breaking on all exceptions causes the debugger to pause
whether or not the breakpoint was caught by application code.
<topic_end>
<topic_start>
known issues
when performing a hot restart for a flutter application,
user breakpoints are cleared.
<topic_end>
<topic_start>
other resources
for more information on debugging and profiling, see the
debugging page.
<topic_end>
<topic_start>
using the logging view
info note
the logging view works with all flutter and dart applications.
<topic_end>
<topic_start>
what is it?
the logging view displays events from the dart runtime,
application frameworks (like flutter), and application-level
logging events.
<topic_end>
<topic_start>
standard logging events
by default, the logging view shows:
<topic_end>
<topic_start>
logging from your application
to implement logging in your code,
see the logging section in the
debugging flutter apps programmatically
page.
<topic_end>
<topic_start>
clearing logs
to clear the log entries in the logging view,
click the clear logs button.
<topic_end>
<topic_start>
other resources
to learn about different methods of logging
and how to effectively use DevTools to
analyze and debug flutter apps faster,
check out a guided logging view tutorial.
<topic_end>
<topic_start>
using the app size tool
<topic_end>
<topic_start>
what is it?
the app size tool allows you to analyze the total size of your app.
you can view a single snapshot of “size information”
using the analysis tab, or compare two different
snapshots of “size information” using the diff tab.
<topic_end>
<topic_start>
what is “size information”?
“size information” contains size data for dart code,
native code, and non-code elements of your app,
like the application package, assets and fonts. a “size
information” file contains data for the total picture
of your application size.
<topic_end>
<topic_start>
dart size information
the dart AOT compiler performs tree-shaking on your code
when compiling your application (profile or release mode
only—the AOT compiler is not used for debug builds,
which are JIT compiled). this means that the compiler
attempts to optimize your app’s size by removing
pieces of code that are unused or unreachable.
after the compiler optimizes your code as much as it can,
the end result can be summarized as the collection of packages,
libraries, classes, and functions that exist in the binary output,
along with their size in bytes. this is the dart portion of
“size information” we can analyze in the app size tool to further
optimize dart code and track down size issues.
<topic_end>
<topic_start>
how to use it
if DevTools is already connected to a running application,
navigate to the “app size” tab.
if DevTools is not connected to a running application, you can