Skip to main content

Cannot Choose Between Multiple Debugging Devices in Android Studio

If  you connect multiple Devices or Emulators to Android Studio and Run Application. Application will only run on the first run device.  It will not ask to select connected device.
ie,
1. If you connect one Device or Emulator
2. Run a project on the device or Emulator
3. Connect another Device or start another Emulator
4. Try to run project on new device
5. It will only run on first device  . will not ask to select Connected Device or Emulators
6. Select Deployment Target Dialog box will not show.

If this Problem occurs to you while Developing on android Studio .  First thing to do is to



  • Stop Application after running on the first device
  • This can be done by clicking Stop app icon which is left of the AVD manger icon.
  • Or by using Keyboard shortcut CTRL+F2
  • Now if you Run the project , Select Deployment Target Dialog box will pop up.
  • You can select another Device or emulator from the list
If still Select Deployment Target window not showing up and project runs on the first device . it will be due to problem with your Run Configuration
  • Go to Run --- Edit Configurations
  • In the General Tab look for Deployment Target Options
  • in that select "Open select Deployment Target Dialog" for target
  • Uncheck  "Use same device for future launches"




this will solve your problem😊

Now if you Run your Application deployment target Dialog will show. then select the device you need




Comments

Popular posts

Android List View using Custom Adapter and SQLite

following is a simple applicaton to create ListView using  Custom adapter.screenshot of the application  is like this . ListView is not used in android Anymore . We use  RecyclerView  and  CardView   in Android RecyclerView Demo is available on the following link http://androidtuts4u.blogspot.in/2017/04/android-recyclerview-example.html RecyclerView with Cardview Example is available on the following link http://androidtuts4u.blogspot.in/2017/09/android-card-view-example.html The ListView below the submit button is populated using Custom Adapter.Data is stored and retrieved using SQLite databsase. you can download the source code of this project from  google drive   https://drive.google.com/folderview?id=0BySLpWhqmbbdUXE5aTNhazludjQ&usp=sharing click on the above link ->sign into  your  google account ->add this to your google drive -> open it in google drive and download it. To create a simple ...

Android Sqlite and ListView Example

This is simple application which insert data into Sqlite database --and shows the data  from the database in a ListView ListView is not used in android Anymore . We use RecyclerView and CardView   in Android RecyclerView Demo is available on the following link http://androidtuts4u.blogspot.in/2017/04/android-recyclerview-example.html RecyclerView with CardView Demo is available on the following link http://androidtuts4u.blogspot.in/2017/09/android-card-view-example.html This  is the first Activity of application which shows data from database in listview. Register here buton will start a Registration Activity. Submit button will add data to database and show it in the ListView of MainActivity. Update can be performed by clicking ListView items.     you can download the source code of this project from  google drive   https://drive.google.com/folderview?id=0BySLpWhqmbbdS0dtT1R2TXdBWEE&usp=sharing click on the abov...

ViewModel with Jetpack Compose

  Compose uses remember API to store object in memory. Stored value is returned during recomposition . remember helps us retain data across recompostion , but when configuration changes happen all stored values are lost . One way to overcome this is to use rememberSaveable . rememberSaveable saves any value that can be saved in a Bundle , so it will survive configuration changes.  But when we are using lot of data , for example a list we can cannot use a rememberSavble beacuse there is limit on amount of data that can be stored in Bundle . So we use ViweModel . ViewModel provide the ui state and access to the business logic located in other layers of the app. It also survives configuration changes. ViewModel handles events coming from the UI or other layers of the app and updates the state holder based on the events. We need to add the following dependency in our app level build.gradle to use ViewModel implementation "androidx.lifecycle:lifecycle-viewmodel-compose:2.4.1" F...