Repository navigation
"no connected devices" when we see an unauthorized device #6538
Description
Activity
- added this to the milestone
on Oct 26, 2016 What do you think the simplest fix is for this? Based on where this call is printed in
flutter_command.dart, other 0-device cases are handled like this:} else if (devices.isEmpty && deviceManager.hasSpecifiedAllDevices) { printStatus('No devices found'); return null; }
However, I don't currently see anything like
deviceManager.devicePendingAuthorizationinDeviceManager.I could see either:
- Adding a method like
devicePendingAuthorizationtoDeviceManager. - Simply changing
No connected devicestoNo available devices.
Number 2 seems less thorough but just as accurate. There's no need to add an additional 'authorized device' state if this error message is the only place that needs it, I would argue.
What do you think?
- Adding a method like
I wouldn't necessarily aim for the simplest fix, but I agree with you that there's nothing really gained from doing anything more involved than just changing the message in this case.
I meant simple in a good way, fwiw.
However, I can't repro the output you show above. Do you mean also for the output of
flutter devices, as shown below?$ flutter --version Flutter 0.7.1-pre.30 • channel master • [email protected]:srsudar/flutter.git Framework • revision 7f0f938de7 (12 hours ago) • 2018-08-27 11:11:14 +0200 Engine • revision af42b6dc95 Tools • Dart 2.1.0-dev.1.0.flutter-ccb16f7282 $ flutter run No connected devices. $ flutter devices No devices detected. Run 'flutter emulators' to list and start any available device emulators. Or, if you expected your device to be detected, please run "flutter doctor" to diagnose potential issues, or visit https://flutter.io/setup/ for troubleshooting tips. • Device 01abfc49119c410e is not authorized. You might need to check your device for an authorization dialog.It's possible this has improved since the original bug was filed.
we met the same question, Have you solved it?
- modified the milestones: ,
on Jan 7, 2020 6 remaining items
- removed this from the milestone
on Jul 22, 2020 - removed this from the milestone
on Aug 17, 2020 - added a commit that references this issue
on Jul 28, 2023 - added 2 commits that reference this issue
on Jul 31, 2023 - added a commit that references this issue
on Aug 2, 2023 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.- locked as resolved and limited conversation to collaborators
on Aug 11, 2023
We shouldn't say "no connected devices" if we see an unauthorized device.