locked
default application is not launching in Emulator RRS feed

  • Question

  • User13293 posted

    I have successfully installed Xamarian Studio and also installed all the required packages at Android SDK Manager, then I created defualt application and try to run it. Emulator is launching but I am not able to see my default app on it. Please help.

    Saturday, June 1, 2013 9:44 AM

All replies

  • User904 posted

    @Bhuwan Could you post build log please?

    Monday, June 3, 2013 10:03 AM
  • User13293 posted

    [2013-06-03 15:37:53.2] INFO: sdk: Looking for Android SDK.. [2013-06-03 15:37:53.2] INFO: sdk: Key HKCU\SOFTWARE\Novell\Mono for Android\AndroidSdkDirectory found: Path contains adb.exe in \platform-tools (C:\Users\sony vaio\AppData\Local\Android\android-sdk). [2013-06-03 15:37:53.2] INFO: sdk: Key HKLM\SOFTWARE\Novell\Mono for Android\AndroidSdkDirectory found: Path does not contain adb.exe in \platform-tools (C:\android-sdk-windows). [2013-06-03 15:37:53.2] INFO: sdk: Key HKCU\SOFTWARE\Xamarin\MonoAndroid\PrivateAndroidSdkPath not found. [2013-06-03 15:37:53.2] INFO: sdk: Key HKCU\SOFTWARE\Android SDK Tools\Path not found. [2013-06-03 15:37:53.2] INFO: sdk: Key HKLM\SOFTWARE\Android SDK Tools\Path found: Path contains adb.exe in \platform-tools (C:\Users\sony vaio\AppData\Local\Android\android-sdk). [2013-06-03 15:37:53.2] INFO: sdk: Looking for Android NDK.. [2013-06-03 15:37:53.3] INFO: sdk: Key HKCU\SOFTWARE\Novell\Mono for Android\AndroidNdkDirectory found: Path contains ndk-stack.exe in . (C:\Program Files\Android\ndk\android-ndk-r8d). [2013-06-03 15:37:53.3] INFO: sdk: Key HKLM\SOFTWARE\Novell\Mono for Android\AndroidNdkDirectory not found. [2013-06-03 15:37:53.3] INFO: sdk: Looking for Java 6 SDK.. [2013-06-03 15:37:53.3] INFO: sdk: Key HKLM\SOFTWARE\JavaSoft\Java Development Kit\CurrentVersion found. [2013-06-03 15:37:53.3] INFO: sdk: Key HKLM\SOFTWARE\JavaSoft\Java Development Kit\1.6\JavaHome found: Path contains jarsigner.exe in \bin (C:\Program Files (x86)\Java\jdk1.6.039). [2013-06-03 15:37:53.3] INFO: sdk: Looking for Android SDK.. [2013-06-03 15:37:53.3] INFO: sdk: Key HKCU\SOFTWARE\Novell\Mono for Android\AndroidSdkDirectory found: Path contains adb.exe in \platform-tools (C:\Users\sony vaio\AppData\Local\Android\android-sdk). [2013-06-03 15:37:53.3] INFO: sdk: Key HKLM\SOFTWARE\Novell\Mono for Android\AndroidSdkDirectory found: Path does not contain adb.exe in \platform-tools (C:\android-sdk-windows). [2013-06-03 15:37:53.3] INFO: sdk: Key HKCU\SOFTWARE\Xamarin\MonoAndroid\PrivateAndroidSdkPath not found. [2013-06-03 15:37:53.3] INFO: sdk: Key HKCU\SOFTWARE\Android SDK Tools\Path not found. [2013-06-03 15:37:53.3] INFO: sdk: Key HKLM\SOFTWARE\Android SDK Tools\Path found: Path contains adb.exe in \platform-tools (C:\Users\sony vaio\AppData\Local\Android\android-sdk). [2013-06-03 15:37:53.3] INFO: sdk: Looking for Android NDK.. [2013-06-03 15:37:53.3] INFO: sdk: Key HKCU\SOFTWARE\Novell\Mono for Android\AndroidNdkDirectory found: Path contains ndk-stack.exe in . (C:\Program Files\Android\ndk\android-ndk-r8d). [2013-06-03 15:37:53.3] INFO: sdk: Key HKLM\SOFTWARE\Novell\Mono for Android\AndroidNdkDirectory not found. [2013-06-03 15:37:53.3] INFO: sdk: Looking for Java 6 SDK.. [2013-06-03 15:37:53.3] INFO: sdk: Key HKLM\SOFTWARE\JavaSoft\Java Development Kit\CurrentVersion found. [2013-06-03 15:37:53.3] INFO: sdk: Key HKLM\SOFTWARE\JavaSoft\Java Development Kit\1.6\JavaHome found: Path contains jarsigner.exe in \bin (C:\Program Files (x86)\Java\jdk1.6.039). [2013-06-03 15:38:30.5] INFO: Starting Android device monitor [2013-06-03 15:38:31.3] INFO: Adb server launch operation completed [2013-06-03 15:38:31.3] INFO: Creating android device tracker [2013-06-03 15:38:31.4] DEBUG: TrackDeviceTask got: [2013-06-03 15:38:31.4] INFO: Got new device list from adb [2013-06-03 15:38:54.4] DEBUG: TrackDeviceTask got: emulator-5554 offline [2013-06-03 15:38:54.4] INFO: Got new device list from adb [2013-06-03 15:39:12.6] DEBUG: TrackDeviceTask got: emulator-5554 device [2013-06-03 15:39:12.6] INFO: Got new device list from adb [2013-06-03 15:39:12.6] DEBUG: RunShellCommand: emulator-5554 getprop [2013-06-03 15:40:10.2] DEBUG: TrackDeviceTask got: [2013-06-03 15:40:10.2] INFO: Got new device list from adb

    Monday, June 3, 2013 10:11 AM
  • User13293 posted

    @Prashant Cholachagudda, Hello Prashant, please see the build log and provide me the solution.

    Monday, June 3, 2013 10:12 AM
  • User13293 posted

    this is the current log after reinstalling and installing Xamarian, please review and help

    [2013-06-04 10:20:27.0] INFO: sdk: Looking for Android SDK.. [2013-06-04 10:20:27.0] INFO: sdk: Key HKCU\SOFTWARE\Novell\Mono for Android\AndroidSdkDirectory found: Path contains adb.exe in \platform-tools (C:\Users\sony vaio\AppData\Local\Android\android-sdk). [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\Novell\Mono for Android\AndroidSdkDirectory found: Path does not contain adb.exe in \platform-tools (C:\android-sdk-windows). [2013-06-04 10:20:27.0] INFO: sdk: Key HKCU\SOFTWARE\Xamarin\MonoAndroid\PrivateAndroidSdkPath not found. [2013-06-04 10:20:27.0] INFO: sdk: Key HKCU\SOFTWARE\Android SDK Tools\Path not found. [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\Android SDK Tools\Path found: Path contains adb.exe in \platform-tools (C:\Users\sony vaio\AppData\Local\Android\android-sdk). [2013-06-04 10:20:27.0] INFO: sdk: Looking for Android NDK.. [2013-06-04 10:20:27.0] INFO: sdk: Key HKCU\SOFTWARE\Novell\Mono for Android\AndroidNdkDirectory found: Path contains ndk-stack.exe in . (C:\Program Files\Android\ndk\android-ndk-r8d). [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\Novell\Mono for Android\AndroidNdkDirectory not found. [2013-06-04 10:20:27.0] INFO: sdk: Looking for Java 6 SDK.. [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\JavaSoft\Java Development Kit\CurrentVersion found. [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\JavaSoft\Java Development Kit\1.6\JavaHome found: Path contains jarsigner.exe in \bin (C:\Program Files (x86)\Java\jdk1.6.039). [2013-06-04 10:20:27.0] INFO: sdk: Looking for Android SDK.. [2013-06-04 10:20:27.0] INFO: sdk: Key HKCU\SOFTWARE\Novell\Mono for Android\AndroidSdkDirectory found: Path contains adb.exe in \platform-tools (C:\Users\sony vaio\AppData\Local\Android\android-sdk). [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\Novell\Mono for Android\AndroidSdkDirectory found: Path does not contain adb.exe in \platform-tools (C:\android-sdk-windows). [2013-06-04 10:20:27.0] INFO: sdk: Key HKCU\SOFTWARE\Xamarin\MonoAndroid\PrivateAndroidSdkPath not found. [2013-06-04 10:20:27.0] INFO: sdk: Key HKCU\SOFTWARE\Android SDK Tools\Path not found. [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\Android SDK Tools\Path found: Path contains adb.exe in \platform-tools (C:\Users\sony vaio\AppData\Local\Android\android-sdk). [2013-06-04 10:20:27.0] INFO: sdk: Looking for Android NDK.. [2013-06-04 10:20:27.0] INFO: sdk: Key HKCU\SOFTWARE\Novell\Mono for Android\AndroidNdkDirectory found: Path contains ndk-stack.exe in . (C:\Program Files\Android\ndk\android-ndk-r8d). [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\Novell\Mono for Android\AndroidNdkDirectory not found. [2013-06-04 10:20:27.0] INFO: sdk: Looking for Java 6 SDK.. [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\JavaSoft\Java Development Kit\CurrentVersion found. [2013-06-04 10:20:27.0] INFO: sdk: Key HKLM\SOFTWARE\JavaSoft\Java Development Kit\1.6\JavaHome found: Path contains jarsigner.exe in \bin (C:\Program Files (x86)\Java\jdk1.6.039). [2013-06-04 10:21:39.3] INFO: Starting Android device monitor [2013-06-04 10:21:39.7] INFO: Adb server launch operation completed [2013-06-04 10:21:39.7] INFO: Creating android device tracker [2013-06-04 10:21:39.8] DEBUG: TrackDeviceTask got: emulator-5554 device [2013-06-04 10:21:39.8] INFO: Got new device list from adb [2013-06-04 10:21:39.8] DEBUG: RunShellCommand: emulator-5554 getprop [2013-06-04 10:22:27.0] DEBUG: TrackDeviceTask got: emulator-5554 device, emulator-5556 offline [2013-06-04 10:22:27.0] INFO: Got new device list from adb [2013-06-04 10:22:45.1] DEBUG: TrackDeviceTask got: emulator-5554 device, emulator-5556 device [2013-06-04 10:22:45.1] INFO: Got new device list from adb [2013-06-04 10:22:45.1] DEBUG: RunShellCommand: emulator-5556 getprop [2013-06-04 10:25:54.6] DEBUG: TrackDeviceTask got: emulator-5554 device [2013-06-04 10:25:54.6] INFO: Got new device list from adb [2013-06-04 10:29:19.8] DEBUG: TrackDeviceTask got: emulator-5554 device, emulator-5556 offline [2013-06-04 10:29:19.8] INFO: Got new device list from adb [2013-06-04 10:29:37.9] DEBUG: TrackDeviceTask got: emulator-5554 device, emulator-5556 device [2013-06-04 10:29:37.9] INFO: Got new device list from adb [2013-06-04 10:29:37.9] DEBUG: RunShellCommand: emulator-5556 getprop [2013-06-04 10:29:52.4] DEBUG: TrackDeviceTask got: emulator-5554 device [2013-06-04 10:29:52.4] INFO: Got new device list from adb [2013-06-04 10:30:21.7] DEBUG: TrackDeviceTask got: [2013-06-04 10:30:21.7] INFO: Got new device list from adb [2013-06-04 10:42:09.0] DEBUG: TrackDeviceTask got: emulator-5554 offline [2013-06-04 10:42:09.0] INFO: Got new device list from adb [2013-06-04 10:42:27.1] DEBUG: TrackDeviceTask got: emulator-5554 device [2013-06-04 10:42:27.1] INFO: Got new device list from adb [2013-06-04 10:42:27.1] DEBUG: RunShellCommand: emulator-5554 getprop [2013-06-04 10:43:28.4] INFO: Stopping Android device monitor [2013-06-04 10:43:28.5] INFO: Adb server kill operation completed [2013-06-04 10:43:28.5] INFO: Starting Android device monitor [2013-06-04 10:43:32.7] INFO: Adb server launch operation completed [2013-06-04 10:43:32.7] INFO: Creating android device tracker [2013-06-04 10:43:32.7] DEBUG: TrackDeviceTask got: emulator-5554 device [2013-06-04 10:43:32.7] INFO: Got new device list from adb [2013-06-04 10:43:32.7] DEBUG: RunShellCommand: emulator-5554 getprop [2013-06-04 10:43:48.8] DEBUG: TrackDeviceTask got: [2013-06-04 10:43:48.8] INFO: Got new device list from adb

    Tuesday, June 4, 2013 5:33 AM
  • User13857 posted

    I have the same problem both in Windows 7 and Windows 8. Both TaskyAndroid and TaskyAndroid_Starter. Both solutions successfully build. Launching the debugger the "Select Device" dialog comes up, but when I select any MonoForAndroid emulator the "OK" button never enables. I can however click "Start Emmualtor" and any of the emulators will successfully start, but never open the app.

    Wednesday, June 5, 2013 1:54 AM
  • User13857 posted

    This is the latest XS.

    Wednesday, June 5, 2013 1:59 AM
  • User13857 posted

    User error...not fully comprehending the documentation. Case closed.

    Thursday, June 6, 2013 10:09 PM
  • User27948 posted

    The case may be closed for you :-) But I got the same problem :-( What was your solution ?? Please help

    Kind regards Bruno

    Sunday, November 10, 2013 6:57 PM
  • User28223 posted

    BrunoBromberg, I am a brand new Xamarin users so there may be a better way to do this but this it what I found out after playing around with the software for a while. First off, the "10 minute guide to building mobile apps in C#" appears to skip several steps in getting good old TaskAndroid running. If someone can point to step by step instructions please chime in.

    This is what I had to do with Visual Studio 2013 & the Android_PaidEdition project. I am using a 30 day trial account that I just setup.

    1) Load all Xamarin software & always get the update if you are prompted. 2) Load the project solution in Visual Studio. 3) In VS - Tools / Open Android Emulator Manager. Select a AVD device. I selected MonForAndroidAPI14. Then press the Start Button. 4) It will take a long time for the device to appear on your screen & display the home page. Mine took 5 minutes. Let it float on your screen and don't login or anything. 5) Right-Click on the TaskyAndroid solution in Solution Explorer and select Configuration Manager 6) In Configuration Manager make sure the Deploy checkbox for TaskyAndroid is selected. Close Window. 7) Run. You will see information about installing applications and framework on device and whatnot. This can take a very long time. Mine took 15-20 mins the first time I did this.
    8) At the end of the deployment verbiage it will finally launch tasky in the emulator for you.

    Good luck and don't give up.

    Wednesday, November 13, 2013 1:31 AM
  • User29373 posted

    Hi, I have the same issue, my app isn't deploy on device :S

    I don't find Configuration Manager in my solution explorer.

    Config:

    Windows 7 pro SP1 32 bits

    === Xamarin Studio === Version 4.2.1 (build 1) Installation UUID: b673d5cd-4f8c-4095-855e-b30af13edfe4 Runtime: Microsoft .NET 4.0.30319.18052 GTK+ 2.24.20 theme: MS-Windows GTK# (2.12.0.0)

    === Xamarin.Android === Version: 4.10.1 (Starter Edition) Android SDK: C:\Users\502115451\AppData\Local\Android\android-sdk Supported Android versions: 2.1 (API level 7) 2.2 (API level 8) 2.3 (API level 10) 3.1 (API level 12) 4.0 (API level 14) 4.0.3 (API level 15) Java SDK: C:\Program Files\Java\jdk1.6.039 java version "1.6.039" Java(TM) SE Runtime Environment (build 1.6.0_39-b04) Java HotSpot(TM) Client VM (build 20.14-b01, mixed mode, sharing)

    === Build Information === Release ID: 402010001 844a84fe0aa0cb5f986d4e3c4807a51487d07845 Build date: 2013-11-13 16:45:15Z Xamarin addins: 97e44e4863da6c479427794457637e75b3d22600

    === Operating System === Windows 6.1.7601.65536

    Wednesday, November 20, 2013 3:44 PM
  • User28 posted

    @GordonFreeman GeorgeMcCoy is describing Visual Studio, which is slightly different to Xamarin Studio.

    When you try to run/debug your app in XS, you will see the device manager come up. It will list any attached devices, running emulators, and non-running emulators. If you do not have any devices or running emulators, select a non-running emulator and press the "start" button. The Android ARM emulator is slow and can take several minutes to start - you will likely have a much better development experience using a device, or an x86 emulator.

    When the emulator is started, it will show up in the list. Select it, and you will be able to continue deploying and debugging the app.

    Wednesday, November 20, 2013 8:08 PM
  • User29438 posted

    From my perspective [an absolute noob], this looks like a bug. Under Win7, I installed Xamarin.Android Starter to drive D: -- my C: is a solid state drive, reserved for system only.

    After installation, XS appears to be utilizing "C:\Users\Scott.android\avd", but the AVD Manager is manipulating files in "D:\Users\Scott.android\avd" [C: vs D:]. During installation, not everything understood the non-default destination.

    How can I direct XS to use the folder on D:?

    Thursday, November 21, 2013 12:38 AM
  • User29373 posted

    @mhutch thanks for the tip but it doesn't work, emulator is selected and started OK but my app isn't deploy. I tried with eclipse and it works but I'm a .net developer so I'd prefer to develop with Xamarin.

    Thursday, November 21, 2013 2:23 PM
  • User28 posted

    @ScottColeman please file a bug including details about how your user profile has been relocated to the D drive. We find the path using .NET's Environment.GetFolderPath (Environment.SpecialFolder.UserProfile), which should respect such things.

    Friday, November 22, 2013 4:04 AM
  • User28 posted

    @GordonFreeman could you please describe step by step what you're doing to deploy your app and how and where it fails, including any error messages?

    Friday, November 22, 2013 4:05 AM
  • User29373 posted

    I downloaded TaskyAndroid project from your website. When the project is opened, I go to Run menu, Start Debugging, the app build successfully after that I select a device (MonoAndroidAPI10 emulator) et click on Start Emulator. Emulator is launched successfully, Android starts successfully but my app is not launched/deployed, I can't find it and there is no error.

    Friday, November 22, 2013 9:29 AM
  • User28 posted

    @GordonFreeman: does the "Deploy to device" pad appear, and if so, what does it contain?

    Saturday, November 23, 2013 9:06 PM
  • User29373 posted

    No it doesn't

    Monday, November 25, 2013 9:07 AM
  • User28 posted

    Can you screencast it so we can see where it fails?

    Monday, November 25, 2013 8:48 PM
  • User29373 posted

    I posted screencast here: http://screencast-o-matic.com/watch/cIXOQpVR8z

    Tuesday, November 26, 2013 9:55 AM
  • User28 posted

    @GordonFreeman after starting the emulator, go back to the device chooser. When the emulator is started, its name in the list will be black text instead of grey. Select it, and click "OK".

    Tuesday, November 26, 2013 5:39 PM
  • User29373 posted

    Ok that works! :) thanks for your help man!

    Wednesday, November 27, 2013 8:47 AM
  • User31412 posted

    Hello, I am using Xamarin 4.2.6 with windows7 ram 1go.When i debug my default app, the emulator is running but it is just black, and it shows only "android" in the middle.Thank you for your help.

    Saturday, December 7, 2013 2:19 PM
  • User28 posted

    @alijaona: That means the emulator is still booting - you'll just have to wait.

    The Android ARM emulator is very slow - much slower than a real device. If you do not have a device, you perhaps could use the hardware accelerated x86 emulator.

    Saturday, December 7, 2013 11:07 PM
  • User31412 posted

    Thank you for your help mhutch, the emulator is working well but, I can't see my applicaction anywhere even in the application list.Can you help?thank you

    Thursday, December 12, 2013 7:30 AM
  • User31972 posted

    I had this issue this morning with a slightly different solution. I switched to release (instead of debug) and it informed me that I didn't have support for the right version of armabi to change I went to project -> options -> Android Build -> Advanced and ticked armabi, the default is armabi v7 which wasn't working for me.

    Thursday, December 12, 2013 11:40 AM