Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Observatory opt-in for debugging, disabled by default for deployed apps #76

Closed
FlutterIssues opened this issue Nov 9, 2015 · 4 comments
Assignees
Labels
c: new feature Nothing broken; request for a new capability

Comments

@FlutterIssues
Copy link

Issue by Hixie
Thursday Jul 16, 2015 at 22:29 GMT
Originally opened as https://github.com/flutter/engine/issues/38


From @Hixie on June 30, 2015 17:2

Copied from original issue: domokit/mojo#284

@FlutterIssues FlutterIssues added this to the Blue Sky milestone Nov 9, 2015
@sethladd
Copy link
Contributor

sethladd commented 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 Hixie added the c: new feature Nothing broken; request for a new capability label Dec 9, 2015
@Hixie
Copy link
Contributor

Hixie commented 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
Copy link
Contributor

This is done. We now have dart_product_mode build flag and exposed to the user as --debug, --profile and --release.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
c: new feature Nothing broken; request for a new capability
Projects
None yet
Development

No branches or pull requests

5 participants