Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-16330

[Android] Deployment to Android emulator ignores saved run configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • 4.30.x
    • 4.1.1.Final
    • aerogear-hybrid
    • None
    • Hide

      Steps to reproduce:
      1. Create a run configuration for a Hybrid Mobile project.
      2. Save the run config with an AVD to use.
      3. Start a different AVD. (I had this running because of a different hybrid mobile project requiring a different AVD).
      4. Run the project by executing: Run As -> Run on Android Emulator, without choosing a Runtime Configuration.
      5. Verify that the project is deployed on the AVD selected in the runtime config (the desired AVD should be started if necessary).
      Step 5 fails.

      Show
      Steps to reproduce: 1. Create a run configuration for a Hybrid Mobile project. 2. Save the run config with an AVD to use. 3. Start a different AVD. (I had this running because of a different hybrid mobile project requiring a different AVD). 4. Run the project by executing: Run As -> Run on Android Emulator, without choosing a Runtime Configuration. 5. Verify that the project is deployed on the AVD selected in the runtime config (the desired AVD should be started if necessary). Step 5 fails.
    • Documentation (Ref Guide, User Guide, etc.)

      The deployment to an emulator is always performed on a currently running AVD even if the runtime config for the project specifies a different AVD.

      Ignore/reject if this is by design. But from the point of view of the user, it would be better to ensure consistency - when a user wants to run his project on a specific AVD, he needs to create a runtime config, but the moment a different AVD is running, this config is ignored.

            Unassigned Unassigned
            vineet.reynolds_jira Vineet Reynolds (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: