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

Flutter plugin doesn't notice new devices if ios-deploy is installed while IntelliJ is running #758

Open
kasperl opened this issue Feb 23, 2017 · 2 comments

Comments

@kasperl
Copy link

kasperl commented Feb 23, 2017

If ios-deploy is installed after IntelliJ has started, it looks like new devices will not be discovered even when they are shown in the listing provided by flutter devices.

Steps to Reproduce

  1. Install Flutter on Mac, but don't install ios-deploy via homebrew just yet.
  2. Install and start IntelliJ with the Flutter plugin.
  3. Create a Flutter project.
  4. Now install ios-deploy and make sure an associated device is listed in flutter devices.
  5. Notice how the new device doesn't show up in IntelliJ.

Version info

[✓] Flutter (on Mac OS, channel master)
• Flutter at /Users/kasperl/Dart/Flutter/flutter
• Framework revision df149c0b4b (4 days ago), 2017-02-19 14:12:57
• Engine revision ab09530927
• Tools Dart version 1.23.0-dev.0.0

[✓] Android toolchain - develop for Android devices (Android SDK 23.0.3)
• Android SDK at /Users/kasperl/Library/Android/sdk
• Platform android-23, build-tools 23.0.3
• Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

[✓] iOS toolchain - develop for iOS devices (Xcode 8.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 8.2.1, Build version 8C1002
• ios-deploy 1.9.1

[✓] IntelliJ IDEA Community Edition (version 2016.3.4)
• Dart plugin version 163.13137
• Flutter plugin version 0.1.10

[✓] Connected devices
• iPod touch • ... • ios • iOS 9.3.4 (13G35)

@mit-mit
Copy link
Member

mit-mit commented Feb 23, 2017

FYI @stevemessick @devoncarew, is the daemon not initialized correctly in this case? I know that you are expected to install ios-deploy first, but as we have seen in the studies users often don't follow the instructions 100% :-)

@devoncarew
Copy link
Member

I think what's happening here is that the daemon is caching some state about the available command-line tools on first access. If so, we should change to not caching, or not caching a failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants