You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Make Observatory opt-in for debugging, disabled by default for deployed apps #76
Is this issue about not shipping the Observatory polymer webapp in our copy of the VM, or about disabling profiling in a production build of a Flutter app?
This bug is about making it possible to connect a debugger to any random deployed app (to get some of the "easy view source" magic that made the Web successful), but requiring an explicit user opt-in to do this (so that random other apps can't just connect to my bank's debugging port and pull out my bank details).
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
sethladd commentedon Dec 8, 2015
Is this issue about not shipping the Observatory polymer webapp in our copy of the VM, or about disabling profiling in a production build of a Flutter app?
Hixie commentedon Dec 9, 2015
This bug is about making it possible to connect a debugger to any random deployed app (to get some of the "easy view source" magic that made the Web successful), but requiring an explicit user opt-in to do this (so that random other apps can't just connect to my bank's debugging port and pull out my bank details).
eseidelGoogle commentedon May 13, 2016
This is done. We now have dart_product_mode build flag and exposed to the user as --debug, --profile and --release.
Don't set Unix file permissions when extracting Dart SDK on Windows (f…
github-actions commentedon Aug 17, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.