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
Better handle x86 / x86_64 issues from launching Android emulators #15055
Comments
Looks like you are using an old Flutter version. |
@zoechi |
I always suggested to just purge the flutter install and reinstall. |
I've deleted my local repo and did a fresh checkout. It works now... but only with following approach:
Device Selector in IntelliJ still brings PANIC error message. And running project from IntelliJ still yields "No Connected Devices Found", allthough I have an emulator running.
I have |
Have you tried restarting IntelliJ (just to be sure)? |
Yes, I've done many things after a fresh checkout
All of this did not help avoiding PANIC error message. |
I'm out of ideas. Can you please add the exact error message. I haven't found it above. |
|
|
cc @devoncarew |
@geekrumper, it looks like the Android Monitor tool from the Android plugins is having trouble executing your emulator image. I would try creating a new one (and you may want to delete the old one as well). I don't believe this is an issue with the flutter intellij tooling per se, but more a local configuration issue, so am closing. Thanks for the report! |
I'm seeing the same error in Android Studio. I can manually start the AVD from the AVD Manager, but when I select it in the toolbar ("Flutter Device Selection") I see the error described above. I have deleted the device and recreated it. |
I am getting the same error. |
This is how I resolved this on Windows 10 where I was getting the same error. %ANDROID_SDK_ROOT% %path% includes these in this order: I guessed that since I was all x64 for all components that IntelliJ might be having a problem with the fact that the out-of-box configured virtual devices over in Android Studio are x86 and not x86_64. My solution was to:
|
@devoncarew please refer to one of my previous comments:
Deleting and creating a new emulator does not solve the problem. And therefore, this issue should be re-opened. In fact I even get this message on a fresh installed machine (OS, IDEA, Android Studio, Sdk, flutter)... |
@cyanfr This leads to an alternative work process
@devoncarew |
I was seeing this same problem when trying to run this with a Nexus 5x API 27 X86 configuration. I created a new Virtual device from intellij, tools > Android > AVD Manager. Pixel XL API 27, and I no longer get this error on the new virtual device. UPDATE: I am on Ubuntu 17.10 |
Hey guys,
|
@geekrumper (and @abarrafo and @cyanfr), thanks much for the analysis and summary! Very useful, and likely an issue that many people are hitting. I only see one copy of |
@devoncarew A couple more things I found that seemed to help. Details in case anyone else stumbles on this thread and they might help.
Added to Path: New Envir Vars:
Then in the specific project structure settings, I set the JDK SDK loc and the Android SDK loc as these did not seem to get picked up any other way. Like so... After this, at least on my Windows 10 box with only 64 bit apps, the AVD images started to work. Although I did get the settings for my new pixel 2 xl image from the ones in Android Studio. Interestingly after I made these changes I could open both x86_64 AND x86 bit AVD images. So not from here (it always produced error): But from here, I would pick an image and start it: And then once the image was started, it interacted just fine with IntelliJ. Then in the project structure specific settings I checked and added the following. |
For what it's worth, i had the same issue in Ubuntu 18.04 and it was solved by doing what @cyanfr mentioned. Can provide more information if it's necessary. |
FYI @DanTup who recently added |
I think this may be a dupe of flutter/flutter-intellij#2351 ? There are two emulator binaries in the SDK and IntelliJ used to use the old one (but has very recently been changed in flutter/flutter-intellij#2383) which would give this PANIC message. For So, I'd be curious to know if anyone having this issue still sees it using |
Closing as dup of flutter/flutter-intellij#2351 |
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 |
Steps to Reproduce
Alternative approach
Screenshots
comments
Logs
Run your application with
flutter run
and attach all the log output.Run
flutter analyze
and attach any output of that command also.Flutter Doctor
The text was updated successfully, but these errors were encountered: