I just installed VS 2015, the installation was finish (after some fail time caused by the slow network, I run setup again).
I create a project as Android > Android blank project
When I press F5, the build is seem to by success but the deploy is fail, there isn't error message. Tried set Tool->Option->Build->Diagnostic, no result. VS 2015 is pretty new, is anyone met this? How can I fix this?
I bumped into the same, but I started VS2015 as Administrator and solved the problem.
Is any Android Virtual Device running?
Open AVD menu
Launch the device
Wait for it to fully load
Build and deploy
Find your app in device's menu and execute it
Visual Studio gets stuck trying to deploy the app to the emulator or the emulator does not appear as a debug target in other IDEs
If the emulator is running, but it does not appear to be connected to ADB (Android Debug Bridge) or it does not appear in Android tools that make use of ADB (for example, Android Studio or Eclipse), you may need to adjust where the emulator looks for ADB.
The emulator uses a registry key to identify the base location of your Android SDK, and looks for the \platform-tools\adb.exe file under that directory. To modify the Android SDK path used by the emulator:
Open Registry Editor by selecting Run from the Start buttons context menu, typing regedit in the dialog box, and choosing OK.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android SDK Tools in the folder tree on the left.
Modify the Path registry variable to match the path to your Android SDK.
Restart the emulator and you should now be able to see the emulator connected to ADB and associated Android tools.
And yet another recipe of fixing this:
clean projects
remove all bin, obj folders
mark your android-project
as startup
then try to deploy again
As for me, in some cases, if visual studio stucked on project building, it requires pc reboot.
I had the same annoying issue. Going to Options -> Xamarin -> Android Setting and checking Preserve application data/cache on device between deploys solved my problem.
I was facing same issue.
Just reopen visual studio and rebuild your project..and then try to deploy.
Its worked for me!
According to Magnus Grindal Bakken's comment, I found the solution.
1) The installation must have an internet connection to be completed.
Any interruption may cause components to be excluded.
2) You need android emulator. Installing the Android SDK and Visual Studio 2015, is not sufficient, You either need the Microsoft emulator, the android one or another third party emulator (like Genymotion). You also need to ensure that the Xamarin plugins for Visual Studio are installed.
Xamarin for Visual Studio can be downloaded here. Once it is installed Visual Studio will be able to create and run Xamarin projects. Xamarin for VS includes the Xamarin Player for emulation. I think it's even better than Genymotion.
Start emulator via AVD manger ... [start] button (as user m93a suggested).
And next option contains check option "wipe user data". Check it !
It helps me solve this problem. Then deploy or debug the application and all process will works as expected.
I had the same problem with my XF App, it didn't deploy and just one message saying Deployment Failed, internal error....
I solved it. Working on Mac with Xamarin Studio, make sure that the ABI of your simulator is supported by your app.
Xamarin Studio Android project Options
Just run your Visual studio as Administrator mode.
Sometimes the physical Android device gets confused about versions.
On the device, to go settings | Applications Manager | All applications.
Manually delete your application.
Manually delete "Mono Shared Runtime" (don't worry it will reinstall during deploy)
Make any change in your project so it is seen as altered and needing to be recompiled: Add a new blank-line to a .cs file or something.
Build
Debug/deploy
I faced that problem couple hours ago, I tried to deactivate hyper-V and it worked for me.
In the Android App project Properties in Visual Studio I had to go to Android Options>Advanced and make sure the Support architectures had the architecture of my AVD checked.
In my case this was x86_64 (which, by the way, does not have a particularly discovereable method of installation - took me days).
First of all, we can find the error in "Details" when we click "Start" button on "AVD Manager" for "Android_Accelerated_x86". If the error is as follows :
Please ensure Intel HAXM is properly installed and usable. CPU
acceleration status: HAXM is not installed on this machine
So, in this case we need to install "Intel® Hardware Accelerated Execution Manager". It can be downloaded from following link :
haxm-windows_v6_0_6.zip (6.0.6)
Note: After installing Xamarin for the first time in visual studio 2015 i had the same error to run "Android_Accelerated_x86". After installing this accelerated emulator is now up and running.
If the emulator does not even lauch, maybe deploy is skipped.
You cas see this in the output console.
If so, you may have to activate the deploy by checking it in the solution's (not project) parameters.
If the emulator launches but the deploy won't end after minutes, with no error, try the steps described here : https://stackoverflow.com/a/32564067/7505268
That solved it for me.
I had Xamarin Android Player opened while trying to deploy the Android project. This steps worked for me:
Closed Xamarin Android Player
Ran Android project again
in my case I had this problem because "Solution Configuration" was set to Release. I change it back to Debug and I solve the problem
Try one of the following and see if you can get the app to deploy to your device.
Clean and build project/solution
Make sure you have updated all the NuGet packages (Right click on solution and click on Manage NuGet Packages.... Then check in Updates section whether there are any updates)
Make sure you have installed all the necessary SDKs from the Android SDK Manager
Check whether you have selected the correct project as the startup
Check if you have set the correct path for Android SDK and NDK locations
Make sure you have checked Deploy for your selected project from Build -> Configuration Manager
Well there can be many reasons,one of them could be that from the Build section in your toolbar,if you check the configuration manager there will be project names that are available in your current solution all you have to check is if the deploy checkbox is checked or not.If not kindly check it and things will work just fine
This worked for me:
Making sure that Define DEBUG constant is checked.
Using Log.Info("yourTag-AnyString", "Error before/after ");
protected override void OnCreate(Bundle bundle)
{
base.OnCreate(bundle);
// Set our view from the "main" layout resource
Log.Info(tag, "Error before Layout");
SetContentView(Resource.Layout.Main);
// Get our button from the layout resource,
// and attach an event to it
//Button button = FindViewById<Button>(Resource.Id.MyButton);
//button.Click += delegate { button.Text = string.Format("{0} clicks!", count++); };
Log.Info(tag, "Error before variables");
userName = FindViewById<EditText>(Resource.Id.editTextUsername);
password = FindViewById<EditText>(Resource.Id.editTextPassword);
btnInsert = FindViewById<Button>(Resource.Id.btnInsert);
Log.Info(tag, "Error after variables");
btnInsert.Click += BtnInsert_Click;
}
changing emulators or exporting the signed .apk instead
For android apps, using android device logging
There is actually a connection between running Visual Studio as administrator and setting the registry path.
I followed the instructions here but it only worked after running VS as admin because my Android SDK path is in "C:\Program Files (x86)". So in order to add or change files there you need admin rights. Alternatively you can change the permissions of the "Android" folder so that the group "Users" as full access. This worked for me as well.
Or you make sure you don't even install the Android SDK in "C:\Program Files (x86)".
By the way I found that restarting VS, or even the Emulator again wasn't necessary after I added the registry key. It picks it up when it needs to.
Hello Installing Android Studio seems to be a nightmare !
I've downloaded this build : android-studio-ide-135.1538390-windows
At the first execution it says that JVM is missing
So I've installed : jdk-8u25-windows-i586.exe
Next run Now I get a message saying that I need an environnement variable to catch the JDK
OK I set it also
Finaly the JDK can be found.... but the nightmare is not finish
I launch Android Studio and try to open a new Project
Now it does not found the SDK which was suposed to come with the IDE
OK back to Download I get : installer_r23.0.2-windows.exe (Very explicit name !!) and I install it
I try again : still no SDK
I keep calm I continue to follow the rules
Your Android SDK is Missing, out of date or is missing Templates
You can configure your SDK Via Configure | Project Default | Project Structure | SDKs
So I try to set
C:\Program Files (x86)\Android\android-sdk
But the IDE refuse to keep that setting
Now I give-up I need some help
Maybe let the SDK installed on Program_Files is not a good idea ?
Thanks for any help
Simple Open the Android Studio.
First click on File menu then Project Structure then you will find an option to set the SDK location. Now instead of writing path simply browse then you are done.
It should solve your problem.
I filed a bug report about that earlier today.
Just start creating or importing a project from the welcome dialog. You should be prompted to supply the SDK path at that point, and (so far) that seems to stick.
Recently i've started android training, and i've got the below 2 issues.
In my desktop i already had eclipse installed, and when trying to import the android plugins, I was getting some error, so what i did was downloaded eclipse+android package from android developers website and I copied it onto my programs files folder where java is installed and when i open it, it is throwing me an error saying the javaw is not found, goinf through the earlier posts on SO website, i've tried the below.
-vm
\adding the java path
But this didn't work for me. so what i did was installed the same package in my laptop(there is no another eclipse on my laptop). and it started working fine.
On my laptop in the eclipse+android package i write a program and when i hit the Android virtual device manager, it asks me to create a AVD, and when i've filled the entire data here, the OK button is still greyed out. Below is the screenshot.
Also i've tried to create by creating from Device definition,even here i'm not getting the ok button hoghlighted and below is its screenshot
please let me know how can i fix the above issues.
Thanks
Firstly you need not wonder for such a mess ..
For IDE purpose .. go to this link .. https://developer.android.com/sdk/installing/studio.html
Android Studio IDE contains all you need .. Just download ..extract and start creating your first Android project.
And now for tutorials to learn .. try these site ..
(1) https://buckysroom.org/videos.php?cat=6 ( Travis ... provide best tutorial in this world )
(2) https://developer.android.com/index.html
Now you are good to go ..
You can see it clearly says: "CPU/ABI: No system images installed for this target"
So either:
Lower your target.
Update your SDK.
Then set a CPU and you can go on in the AVD creation process.
update the sdk, install ARM/intel(x86) for CPU/ABI
Try using Android Studio by IntelliJ ,as it is for more better than eclipse and moreover ADT plugin for Eclipse is no longer in active development.
if you then also get the same error again try this link android Developer and setup java environment.
As the title reads, it crashes every time I make a new android app project. It seems to run fine when I make a new Java project, however. The error code i get is: Java was started but returned with exit code: -805306369.
That's all I could post, i can't seem to copy the error message (it's a pop-up, doesn't appear on console)
Just as it's about to load the project, eclipse goes Not Responding for a long time, so I'm forced to close it and I get that error message.
Any help would be appreciated, thank you.
If you're using Eclipse to build Android, do the following in order:
Install the JDK from Oracle. You can get the JDK here.
Install Eclipse (e.g. Eclipse Standard version). As of November 2013, Juno (Eclipse v4.2.2) is the most stable release of Eclipse. Refrain from using Kepler release for now. You can get old, stable release of Eclipse here. Or, new version here if it is stable. Important: When you install Eclipse, do not overwrite an existing Eclipse installed directory but instead create a new directory and install Eclipse there. This would prevent getting libraries mixed up between different versions of Eclipse.
Install the Android SDK. You can get the SDK here. For beginners, choose the installer_r22.3-windows.exe package.
Install the Android Development Tools (ADT). You can get the ADT here.
Start Eclipse.
From Eclipse's menu, select Window | Preferences. Then, select Java | Installed JREs option. Check to see if Eclipse has listed correctly the JDK installed directory created from step 1 above. If not, click Add button and browse to your JDK installed directory. On Windows, this directory is normally found under C:\Program Files\Java\jdk1.6.0_45 (e.g. Java 1.6 release 45).
In Eclipse's Preferences screen, select Android option and check that the directory of the Android SDK Location is correct. It should be correct if you have successfully completed step 3 above.
To create a new Android project, from Eclipse's menu select File | New | Android Application Project. Fill in the required information in the New Android Application screen and click Finish when done.
OPTIONAL: Under Eclipse's Window menu option, there are two Android submenu options: Android SDK Manager and Android Virtual Device Manager.
a. The Android SDK Manager option allows you to install/remove versions and/or components used for Android development.
b. The Android Virtual Device Manager option allows you to create virtual Android devices for development and testing purposes. For example, an Android virtual device with a Target of Android 2.1 - API Level 7 will allow you to test your Android application that will later run in production on devices - phones, tablets, notes - that run Android firmware version 2.1.
I am new to the android development and when i create a new project using eclipse juno on mac OSx i got an error at runtime Failed to instantiate com.android.menubar.internal.MenuBarEnhancerCocoa
And yes on the layout file it also says- The project target(Android 4.1) is not properly loaded.
Anyone please help me how to get out of this. Thanks in advance..
And yes everything was setup properly SDK and all, because this whole setup is running properly on one of the other system.
I had the same problem but managed to resolve it. com.android.menubar.internal.MenuBarEnhancerCocoa - was not in the SDK that was linked to Eclipse install (I have multiple for various reasons - e.g. AppEngine not supported in latest Eclipse). There were a number of steps I had to do to resolve this (so any one of them may be the actual fix or a combination may resolve the problem).
Here's a checklist :
If you have installed Eclipse - click the Android SDK manager icon. Ensure it is pointing to the latest Android SDK (R20 as of writing)
As it's a new Eclipse+SDK - add the build targets by selecting from the list of targets that appear in the SDK manager. Also add Android support tools
Restart Eclipse. When asked about he workspace - create a new one. I thought some of my problems would be linked to old projects.
The problems should have gone away. One final thing is, once you create a project - check your certificates have not expired. There's another thread on updating the debug certificate (Delete your keystore located in ~/.android/debug.keystore then restart Eclipse.)
Create a new AVD target.
Hope those things help.
It appears to me the com.android.menubar.internal.MenuBarEnhancerCocoa is only there to make the android app feel nicer if it's run directly. Then preferences and about will be in the application menu. If you run the android sdk manager from eclipse, then eclipse will take over that part of the application menu.
Although it doesn't sort out the issue it may be useful anyway. There's the web page with the sources MenuBarEnhancer where there's the call to instantiate the com.android.menubar.internal.MenuBarEnhancerCocoa class.