flutter - not detecting adding AVM
As you can see from the gif, I have two AVDs set up. I can access them from the AVD Manager, however cannot add them to target selector.
I have restarted android development studio multiple times and still experiencing the same behaviour. Flutter doctor shows no error aside from no connected devices. I have the latest versions of all software as downloaded it today.
How do i overcome this behaviour?
Gif detailing faulty adding behaviour
android 
flutter asked Nov 24 '18 at 20:34
Colleen SheridanColleen Sheridan
1
add a comment |
As you can see from the gif, I have two AVDs set up. I can access them from the AVD Manager, however cannot add them to target selector.
I have restarted android development studio multiple times and still experiencing the same behaviour. Flutter doctor shows no error aside from no connected devices. I have the latest versions of all software as downloaded it today.
How do i overcome this behaviour?
Gif detailing faulty adding behaviour
android flutter asked Nov 24 '18 at 20:34
Colleen SheridanColleen Sheridan
1
Find adb from the command line and tryadb kill-server, restart Android Studio, and try the emulator again.
– Morrison Chang
Nov 24 '18 at 21:14
also on my device this is not running as expected and I think you could file an issue on github. Even after adb kill-server and restart, I can start the emulator with Android Studio, but afterwards have to select a new entry "Android SDK built for x86" in the device-selector to actually start the app on the emulator. Maybe this is still a solution for you to get running.
– Christian
Nov 24 '18 at 22:47
add a comment |
As you can see from the gif, I have two AVDs set up. I can access them from the AVD Manager, however cannot add them to target selector.
I have restarted android development studio multiple times and still experiencing the same behaviour. Flutter doctor shows no error aside from no connected devices. I have the latest versions of all software as downloaded it today.
How do i overcome this behaviour?
Gif detailing faulty adding behaviour
android flutter asked Nov 24 '18 at 20:34
Colleen SheridanColleen Sheridan
1
As you can see from the gif, I have two AVDs set up. I can access them from the AVD Manager, however cannot add them to target selector.
I have restarted android development studio multiple times and still experiencing the same behaviour. Flutter doctor shows no error aside from no connected devices. I have the latest versions of all software as downloaded it today.
How do i overcome this behaviour?
Gif detailing faulty adding behaviour
android flutter android flutter asked Nov 24 '18 at 20:34
Colleen SheridanColleen Sheridan
1
asked Nov 24 '18 at 20:34
Colleen SheridanColleen Sheridan
1
asked Nov 24 '18 at 20:34
Colleen SheridanColleen Sheridan
1
asked Nov 24 '18 at 20:34
Colleen SheridanColleen Sheridan
1
asked Nov 24 '18 at 20:34
Colleen SheridanColleen Sheridan
1
1
Find adb from the command line and tryadb kill-server, restart Android Studio, and try the emulator again.
– Morrison Chang
Nov 24 '18 at 21:14
also on my device this is not running as expected and I think you could file an issue on github. Even after adb kill-server and restart, I can start the emulator with Android Studio, but afterwards have to select a new entry "Android SDK built for x86" in the device-selector to actually start the app on the emulator. Maybe this is still a solution for you to get running.
– Christian
Nov 24 '18 at 22:47
add a comment |
Find adb from the command line and tryadb kill-server, restart Android Studio, and try the emulator again.
– Morrison Chang
Nov 24 '18 at 21:14
also on my device this is not running as expected and I think you could file an issue on github. Even after adb kill-server and restart, I can start the emulator with Android Studio, but afterwards have to select a new entry "Android SDK built for x86" in the device-selector to actually start the app on the emulator. Maybe this is still a solution for you to get running.
– Christian
Nov 24 '18 at 22:47
Find adb from the command line and try
adb kill-server, restart Android Studio, and try the emulator again.– Morrison Chang
Nov 24 '18 at 21:14
Find adb from the command line and try
adb kill-server, restart Android Studio, and try the emulator again.– Morrison Chang
Nov 24 '18 at 21:14
also on my device this is not running as expected and I think you could file an issue on github. Even after adb kill-server and restart, I can start the emulator with Android Studio, but afterwards have to select a new entry "Android SDK built for x86" in the device-selector to actually start the app on the emulator. Maybe this is still a solution for you to get running.
– Christian
Nov 24 '18 at 22:47
also on my device this is not running as expected and I think you could file an issue on github. Even after adb kill-server and restart, I can start the emulator with Android Studio, but afterwards have to select a new entry "Android SDK built for x86" in the device-selector to actually start the app on the emulator. Maybe this is still a solution for you to get running.
– Christian
Nov 24 '18 at 22:47
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53462133%2fflutter-not-detecting-adding-avm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53462133%2fflutter-not-detecting-adding-avm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Find adb from the command line and try
adb kill-server, restart Android Studio, and try the emulator again.– Morrison Chang
Nov 24 '18 at 21:14
also on my device this is not running as expected and I think you could file an issue on github. Even after adb kill-server and restart, I can start the emulator with Android Studio, but afterwards have to select a new entry "Android SDK built for x86" in the device-selector to actually start the app on the emulator. Maybe this is still a solution for you to get running.
– Christian
Nov 24 '18 at 22:47