I don't understand...
In my office I installed Eclipse + Android SDK (API 16) + ADT plugin to develop my own app. When I installed it on my Galaxy Tab and Galaxy Nexus nothing happened and it worked fine. But when I installed all of this on my laptop in my house and imported the eclipse project to installed it again on my devices ADT says that message: "No compatible targets were found". Despite it's the same project, i didn't change a thing and the software is the same...
What can be causing this issue? Any ideas?
I have a meeting this wednesday to start selling the app and it would be great if someone could answer me before that day!! xD
Thanks!!
Are the ADB drivers for the phone working/installed on the laptop?
if your using windows check the device manager.
It sounds like you don't have the proper version of the SDK installed on your Eclipse. You need to make sure you have used the 'SDK Manager' to install the proper Android version, that your build is compiling to what you expect (this is set in the AndroidManifest.xml), and that your emulator or device is targeting the version of the OS you are expecting.
My quess is you don't have the proper Android SDK downloaded.
Related
I'm just starting Jesse Liberty's new Pluralsight course, "Building Your First Mobile Application with Xamarin.Forms and Visual Studio 2017" and I'm running into a problem right out of the gate.
In the video, Jesse creates a new Xamarin.Forms project, modifies the XAML a bit, and runs it. Here is a screenshot of his list of emulators:
I've disabled Hyper-V, and installed the latest Intel HAXM.
I've followed along step-by-step, using the latest version of VS2017 (installed yesterday, no updates available), and I've used the Android SDK Manager to install the SDK Platforms APIs 23 - 27. More specifically, I've installed every available option for Android 6 (API 23), which is what shows in Jesse's list.
I have set the following Android project Properties:
Application :: Target Framework = Use Latest Platform (Android 8.0 Oreo)
Android Manifest :: Minimum Version = Android 6.0 (API 23 - Marshmallow)
Android Manifest :: Target Version = Android 8.0 (API 26 - Oreo)
When I open the dropdown, I don't even see the VisualStudio_android emulators at all, and I'd assume they come preinstalled with VS2017 when I install Xamarin, but no:
I have no idea where to get the Visual Studio emulators; but, as I understand it, they run much faster than others so figuring this out will probably be worth my time.
The Android Virtual Device (AVD) Manager doesn't list the VS emulators, so I can't add them from there. I know there is an Android emulator from Microsoft but it says it's Hyper-V compatible, and I've just disabled Hyper-V to use the other emulators. Is this a good choice? Are these the emulators I'm missing?
I'm out of ideas - what's my next step?
They have been renamed to streamline development. We only install a minimal amount of emulators. They used to be named visualstudio_ and now just android_ but you can create as many as you want.
I use intel haxm x86 emulators from google.
It turns out, the emulators weren't installed for some reason when I installed VS2017 and the Mobile Development Workflow.
I went into the "Individual Components" tab in the Visual Studio Installer, checked the emulator boxes, and all the emulators show up fine now.
Try uninstalling visual studio and then installing it again (save your projects first) and make sure that you install the Microsoft Visual Studio Emulator for Android. Check everywhere in the installation guide (Specifically under Cross platform mobile development). You might have missed it during your installation process.
Wrote app for an android device whose installed Android version is Lollipop 5.1 (AZPEN A1040 tablet - latest version available for it).
The app installs and works correctly in the emulator (setup to emulate a Lollipop 5.1 device)
However, after archiving without any issues, when attempting to install the app's apk file to the actual target device, I get the following error:
"There was a problem parsing the package"
The project's properties in Visual Studio 2015 are displayed in the graphics below:
All the referenced libraries in the project are shown in the picture below:
I have neither errors nor warnings during the build, deploy to emulator or archiving processes.
The target device has already the following settings enabled:
"Allow installation of apps from unknown sources"
"USB Debugging" (installation has been attempted with this setting on or off without success)
EDIT: To add pertinent info based on comments below
The apk is signed (previously archived apks have worked correctly.
New code has been added since those working apks, but as mentioned I
have no errors or warning when building the latest apk).
Have not tried archiving in Debug mode (not sure if it will let me,
not sure I'd like to try since this is for a client).
The apks are named during archiving process. After the creation,
apk file's name has not been changed(I did change the 'suggested'
name to something shorter during the archiving process, but did it so also for the previously working apk vesions whose installation worked on the target device).
At this point I'm at a loss as to what to do to make this install on the target device.
Any ideas?
I was receiving this issue and the problem was because I had multiple versions of the "Android SDK Build Tools" installed.
To see if you have this, go to the Android SDK Manager, and look under Tools.
If you have multiples, uninstall all the extra ones and rebuild your package.
As soon as I did this, I was able to deploy/install this package w/out hassle.
Note that the package that wouldn't install on the device WOULD install in the emulator(I'm using Visual Studio Emulator for Android).
Figured it out what the issue was. The settings on the device under "About Tablet" displayed the Android Version as 5.1. Because of that, I set the Minimum Android Target in the Visual Studio project as "Android 5.1 (API Level 22 - Lollipop)".
After reading #Jon_Douglas' comment, I decided to bite the bullet and ask the client to let me use his device for troubleshooting. Once I connected the device, Visual Studio picked it up as "AZPEN A1040 (Android 5.0 - API 21)".
I changed the Minimum Android Target to "Android 5.0 (API Level 21 - Lollipop)" and was able to install the apk. Compare the settings image below to the one initially provided above:
I have updated my android version from 4.1.1 to 4.2.2 on google Nexus 7, (Worked Perfect Before)After that unfortunately i can't debug my App anymore,i can see my device on "Android Device Chooser" page but i can't select it, and ok button is not Active. my minsdk version is 12 and in that page written that "Select a device compatible with Target android 3.1"!.i'm developing on Motodev Studio, i'm working on this for hours but i don't know what causes this issue ,any help would be appreciated
According to this post
there were some packages missing, which weren't shown in the Android SDK Manager,so after reload on Sdk manager and installing missing packages my problem had been solved!
I'm developing a taxi order application for Android. Two days ago I got stuck with a problem that I couldn't use Internet on emulator - it refused to work. The cause was in network settings in Windows, but I learned it later. That time I just tried to reinstall Android SDK hoping everyrhing will be repaired. Before that I was working with revision 16. Now I installed revision 20. My Eclipse ADT plugin automatically updated to support newer SDK version.
Now I work without real device and test everything on Android emulator. Today I sent the newest release of my app to my chief but I refused to be installed. The minimal SDK version is 8 (2.2), and the chief has an Android 2.3 device. He tried to install this app onto other two devices. Another 2.3 device also declined apk, but a 2.2 device accepted it. What's the problem? Note that I didn't set max SDK version. I also tried installing and running my application an a 2.3 emulator, everything was fine.
P.S. Problem solved, see Tim's suggestion below.
If he had an old version installed have him try uninstalling that first. My guess is that you got a new debug key and it is failing install due to different keys.
I recently downloaded and installed Eclipse Java EE IDE: Indigo Service Release 2. I made a simple application that runs well on the emulator; now I want to try and run it on my android mobile device. From the Android Developers site, I followed the instructions to do so until I got to the point where I needed to locate the USB driver folder for the Google USB driver found in sdk\extras\google\usb_driver. I do not have that driver, so I went on to download it. I was told it was found in the SDK manager under "Extras". I proceeded in Eclipse to Window > Android SDK Manger. I waited for it get done fetching and then went to "Extras". Making sure "Updates/New" was checked as well as "Installed"; however, the only thing under the "Extras" tab is "Android Support Package" and nothing else.
And so here I am ... stuck on what I need to do.
Any help would be greatly appreciated.
http://developer.android.com/sdk/oem-usb.html
You can get the USB drivers for most devices from the manufacturer's site listed here.
As far as the Google USB drivers, I would ensure you are running the latest version of the Android SDK tools and to try running the program as admin.
I just noticed that bringing up the SDK manager from within Eclipse will not show the Google USB driver... However, opening it up via the Start Menu will. (Also, run it as Administrator).
I was having a similar issue and I traced my root cause to this error. I forgot to install Google USB driver. This can be done via SDK manager, ie Android studio->File->Settings->Appearance and behavior->System Settings->Android SDK in tab "SDK tools" check the option for "Google USB Driver" and Apply.
I was having a similar issue and I traced my root cause to this error message in the log.
XML verification failed for http://dl-ssl.google.com/android/repository.addon.xml
If this is the case, make sure your JDK/JRE version is 1.6 or greater.
If you are using Windows 7 64 bit, make sure you update your x86 JDK/JRE version as well.