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

"Run on Android emulator" fails for AVDs with Google APIs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.2.0.Beta2
    • 4.2.0.Beta1
    • aerogear-hybrid
    • None
    • Hide

      1. Create a new AVD. Specify the target as "Google APIs (Google Inc.) - API Level 19" (if Android SDK for 4.4.2 is installed, level 19 should be available).
      2. Attempt to run a Hybrid Mobile app using the "Run on Android Emulator" option, using the created AVD.
      3. The build and deployment will fail with the reported message.

      Show
      1. Create a new AVD. Specify the target as "Google APIs (Google Inc.) - API Level 19" (if Android SDK for 4.4.2 is installed, level 19 should be available). 2. Attempt to run a Hybrid Mobile app using the "Run on Android Emulator" option, using the created AVD. 3. The build and deployment will fail with the reported message.
    • Workaround Exists
    • Hide

      Export the application as a native platform project.
      Run the project on the emulator using the native Android project using ADT.

      Show
      Export the application as a native platform project. Run the project on the emulator using the native Android project using ADT.

      The build and deployment to an AVD with target "Google APIs (Google Inc.) - API Level X" fails with the following error message:

      An internal error occurred during: "Launching Push-Demo (Android Emulator)".
For input string: "rget: Google APIs (Google Inc."

      Recreating the AVD as a 'normal' one lacking Google APIs gets around this issue, but is not a suitable workaround for testing Cordova apps that depend on plugins requiring the Google APIs (like the Aerogear Push plugin that relies on GCM). Without the Google APIs, the GCM service intent will not be invoked, and thus apps will fail to register themselves against a Unified Push Server.

      Additionally, the presence of this AVD prevents new Run configurations from being created or existing ones from being modified. Creating a new Android emulator configuration via Run -> Run As -> Run Configurations ... results in the same error.

            gercan@redhat.com Gorkem Ercan
            vineet.reynolds_jira Vineet Reynolds (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: