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
Pick the right observatory when multiple are available #2722
Comments
How do you get into the state where this happens? Where do these IDs come from? Are they the same for each version of the app, or different for each platform? VS Code doesn't currently know anything about the file structure of the native apps, so if they're in there I don't think we should go fishing for them. Maybe it would be better if there was a JSON version of this error (in @jonahwilliams what do you think? We already have some daemon-to-client requests (for |
I think it was just from running one Flutter app, not closing the app (such as launching from CLI then detach). Repeat for a second app. Then go to VSCode for one of the projects and attach to Flutter on device. |
This issue has been marked stale because it is tagged awaiting-info for 30 days with no activity. Remove the stale label or comment to prevent the issue being closed in 10 days. |
Perhaps another simpler option here would be for |
The tool could try and determine whether their is a usable identifier in the current project. If a terminal attached, we could prompt with the default being the detected project if found. If there is no terminal we can select the detected project, or exit if no project was detected. WDUT? |
Yeah, that sounds good to me. I'm not sure how to do it though - I'm guessing this is iOS-only (from searching for the error) and probably starts with passing |
Sometimes when I attach to the selected device, I get
But theoretically, VSCode should know what the currently open project's app id should be and should just send it along.
The text was updated successfully, but these errors were encountered: