I'm getting an error when trying to debug my AIR app on Android, "Device appears to be offline". It used to work. I have AIR installed. I'm not sure what changed. I think maybe AIR was updated and that changed something but I'm guessing.
I've attached an image.
I've restarted the device a few times. I'm using Flash Builder 4.7. I have AIR 3.6.0.597 installed. USB Debugging is enabled. It's also connected as a Media device (MTP) which I may have accidentally turned on (but I'm not sure and it doesn't seem there's a way to turn this off).
I also recently updated to Jelly Bean 4.2.2 and now Flash Builder shows the same thing.
Adobe AIR Version: Not installed
State: Offline
OS: Windows 8.
Device: Nexus 7.
IDE: Flash Builder 4.6.
AIR: 3.4.
As mention above by 1.21 gigawatts pointed out a link that goes to a thread with this suggestion:
Same boat, from
\android-sdk\platform-tools copy theses
files : aapt.exe, adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and dx.jar
(under lib rep) and paste into \lib\android\bin
To check, tape in cmd $ adb.exe version, you should have 1.0.31
instead of 1.0.26 Voilà!
The fresh updated sdk can be found here: http://developer.android.com/sdk/index.html#download
Going to see if the sdk update helps at all. Will report back "shortly".
[UPDATE]
Works for me! Thanks for posting that link 1.21 gigawatts. Yep, the problem is the new RSA key needed for the device to communicate with your computer.
I copied files listed above into the the flex air sdk. You need to confirm communication with your computer on your Nexus 7. There is a little popup prompt asking if you want to allow communication with the computer. After confirming refresh the device list; the device will show up correctly and you can get back to life as normal.
To those what would downvote the original question just because all the information was not supplied I have following to say. I found what I needed without every little detail included in the question. Questions do not need to be perfect and simple "cookie crumbs" are useful. sigh I wonder how much useful information is lost because of this behavior.
So here's how I got debugging to work for the following.
I'm using Mac OSX 10.8.2, Nexus 7, Flash Builder 4.7 and AIR: 3.6.
Download the latest Android SDK here: http://developer.android.com/sdk/index.html
Unzip it and copy aapt, adb and dx.jar from the [android-sdk]\platform-tools\ directory (dx.jar is in the \platform-tools\lib directory).
Paste these files in the [FLEX_SDK_AIR_3.6]\lib\android\bin directory.
Restart Flash Builder
I think the dx.jar is necessary when creating the release build.
There's another issue that may be related, Error SDK component at air/android/device/runtime.apk is out of date. Still trying to figure this one out.
If you're not able to find aapt after downloading the sdk from the link given, you need to go to Terminal and from the "tools" folder type:
./android update sdk
Then check build-tools
Also, for me it still didnt work until I updated Adobe AIR SDK to latest (using rsync not regular copy), and finally copy android-sdk-mac_x86/platforms/android-xx/android.jar to [air-sdk-version]/lib/android/lib/android-res.jar
Related
I am trying to to run a application on my android device. The issue is that I get the PAClient error E0002 From my understanding profile names are only needed when running apps on Remote Devices, which I'm not doing. There are no profiles created for the PAClient and even if i try to create one the only option is Widows 64 and 32-Bit
I recently reinstalled the Android Common Files from Tools -> Manage Platforms. That could have something to do with it. I know there is another post here, but that post has no working answers.
Also here are my computers environment variables
My platform selector
So how do I fix this error?
The Answer:
The PAClient Error was caused by a compatibility issue with the device in question and the Android SDK Installed the computer.
To fix this issue go to C:\Users\Public\Documents\Embarcadero\Studio\21.0\CatalogRepository\<Your Installed SDK>\ open SDK Manager.exe, remove the SDK installed (Ex: Android 10) and install the one corresponding to the Android Version on your phone (Android R Dev. Preview in my case). Then open Delphi, go to Tools -> Options -> Deployment -> Sdk Manager then change the path of the old SDKs to the new SDK path (They should have a exclamation mark next to them). Now the last thing you have to do is go to the Java Tab and change the Keytool and Jarsigner location to a valid one if its not already valid (something like C:\ProgramFiles\<your java installation>\<java jdk version>\bin\keytool.exe and C:\ProgramFiles\<your java installation>\<java jdk version>\bin\jarsigner.exe for the jarsigner).
That's all. Now you can compile & run your application on your device.
Note: You don't have to uninstall the old SDK if you still need it to make apps for other android versions. Only remove it if you don't need it.
This sort of thing has already been asked about a couple of times before, but the advice I've seen hasn't fixed my problem. I'm starting to work on an AIR Mobile project in Flash Builder 4.7 (it was 4.6 yesterday), and it doesn't want to debug directly on a Samsung Galaxy Pro Tab 8.2 my boss has handed me. When I try to run the application, written in AS3, it just keeps showing the device as offline.
It's been recommended to:
update USB drivers - done
update adb.exe to 1.0.31 - done
check "USB debugging" on the device - done
run "adb devices", then accept the RSA signature thing - done
What else is there?
EDIT
Something to note is that there doesn't seem to be a "charge-only" mode on the device; at least some versions of KitKat stripped out a couple of the options for the USB mode.
Also I've tried previously to download the following files from Android and to update my Flex SDK with them:
aapt.exe
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
dx.jar
Unfortunately I couldn't get that to work earlier. When I saw it posted about previously, somebody said that the "right versions" of those files would all be within a single, specific folder within an Android SDK folder - <Android root>\android-sdk\platform-tools - but I only had three of them in that folder; so within the Android downloads, I had to hunt around a little and pull them from different spots.
For example, I would pull aapt.exe from <Android root>\android-sdk\build-tools\21.1.2, and I would pull dx.jar from <Android root>\android-sdk\build-tools\21.1.2\lib.
Maybe that means the versions I copied over weren't correct? I've tried using the Android SDK Manager to get them, but it doesn't seem to want to get them all and put them in the same spot and/or get all the right files in the first place. If somebody could show me a repository for the right versions, or at least a way to make sure I'm downloading the right versions, I can try it again to see if that might end up being the answer.
Also if I go into the command prompt as an administrator and navigate to the folder adb is in for Flash Builder, and if I run adb from there, this is what I get:
>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0e5d4a10064eb62c device
However this is a problem that's widely attributed to HTC, which my computer doesn't have anything to do with.
Basically you need to update a few files in the AIR SDK with those of the latest Android SDK.
Please refer to this topic's answer:
https://forums.adobe.com/message/6794404#6794404
Jan led me to the problem by making me look closer at the situation with those files.
TL;DR
If you're using Flash Builder 4.7, paste the files on that list to <Flash Builder root>\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib\android\bin.
If you're using Flash Builder 4.6, paste them into <Flash Builder root>\sdks\4.6.0\lib\android\bin.
Elsewhere on the Internet, it had been said to paste those files into <Flash Builder root>\sdks\4.6.0\lib\android\bin, but it turns out there was another Flash Builder folder with adb.exe in it, <Flash Builder root>\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib\android\bin. Also whereas I seem to remember the first folder's original contents containing a partially different list of files, the second folder's original contents had exactly the same list of files - just older versions of them.
That being said, after I originally posted this answer, the advice I found on the Internet about putting them in the first folder turned out to be quite true if and only if you're using Flash Builder 4.6; I updgraded to Flash Builder 4.7 while in the process of trying to fix this problem, and my guess is that I didn't try that particular bit of advice out until after I had upgraded. This would have caused that advice to fail, as it's at least somewhat specific to 4.6.
As for 4.7 though, essentially I was getting that "server out of date" error when I would try to run adb on the command line, and the usual ADB fixer download (adbfix.exe) actually didn't help very much, but information on the Internet described the "server out of date" issue as being a problem with HTC (whatever that is) coming with its own adb in its own folder that is effectively out of sync with whichever adb you're really trying to use. This would cause a sort of runtime conflict between the two. However I didn't have HTC or a folder by that name, so after Jan nudged me back in the right direction, I finally just ran a search for adb.exe in my Flash Builder root directory, and that's when I found the second folder.
So essentially, having already copied and pasted updated versions of all the files on that list into the first folder (I still got them from three different folders within the Android SDK Manager's directory), I pasted them once more into the second folder. With both folders containing relatively current versions, and having also done other steps like allowing USB debugging on the device and allowing RSA signatures from my desktop or whatever, it was finally able to work, and I was able to debug the AIR Mobile program directly on the device.
I'm a little curious as to whether even more recent versions of those files tend to break this, or whether you can use any version that's been made for a target of at least 4.4.2. In the end, my adb version is 1.0.32, not 1.0.31, but I did at least try to come close to something that was tailored toward the Android 4.4.2 KitKat.
Earlier I was also unsure of whether these files had to be pasted into both folders, but now I know that they don't. As far as I know, in FB 4.7's case, pasting them into both folders doesn't hurt anything, as I was able to debug on the device with them having been pasted into both. After originally posting this answer though, I reinstalled 4.7 and just pasted those files into the second folder, but not the first one, and it was still able to work just fine. Finally I reinstalled 4.6 as well, but even an equivalent to the second folder didn't seem to be in its installation folder; only the first folder did, so I just pasted the files into there, and that managed to work as well.
So essentially, get updated versions of these files:
aapt.exe
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
dx.jar
from Android SDK Manager (namely, make sure they're compatible with Android 4.4.2), and paste them into the proper SDK folder, which depends on which version of Flash Builder you're using:
4.7: <Flash Builder root>\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\
lib\android\bin
4.6: <Flash Builder root>\sdks\4.6.0\lib\android\bin
And of course, if you're using a slightly different minor version of the Eclipse plugin in FB 4.7's case, you might have to change the path slightly to match the version number.
I'm trying to setup Android Studio on a new install of Mac OS X Yosemite. I downloaded the Android Studio Beta v0.8.14 from here: https://developer.android.com/sdk/installing/studio.html and upon launching it complained about not having an SDK (although the download page indicates it should include the SDK). I tried searching after installing for the SDK and can't find it (a few other posts indicate /Applications/Android Studio.app/sdk but that location doesn't exist). Where is the SDK installed and what is required to set it up?
Go to the SDK Manager and click Edit... next to the field for the location of the SDK. Then an "SDK Setup" window should display. There you can download the SDK.
Edit: This answer is deprecated as Android Studio seems to bundle everything since a while already.
Old answer
It seems the android-studio-bundle version is no longer available in the download page (instead there are only android-studio-ide). When you start Android Studio, it won't let you create a new projet until you configure the SDK location.
That means you have to download the SDK separately here, extract it somewhere, and configure it on Configure->Project Defaults->Project Structure. After that, the SDK Manager icon will be enabled and you can download the tools you want.
I had the same problem on Windows. After I re-installed it a few times, I found that the SDK was installed but hidden in C:\Users\<user name>\AppData\Local\Android\sdk.
Information for Windows
For some reason, which I have no time to investigate, Android seems to provide, currently, the IDE and the SDK separately, while in the Dev Webpage says the opposite.
This is the "complete" (false!) tool I have just downloaded: android-studio-ide-171.4443003-windows.exe (SDK is missing here, note the "ide" in the file name).
And this is the real complete tool I had downloaded few months ago, from the same place...: android-studio-bundle-162.3871768-windows.exe
Note that this last one has the "bundle" in the file name.
Please, download the bundle (IDE+SDK) from here:
https://dl.google.com/dl/android/studio/install/2.3.1.0/android-studio-bundle-162.3871768-windows.exe?hl=ko
I want to suppose (¿?) that similar link you can find for Linux or macOS just Googling for it.
Hope this helps!
It worked like this for me
Downloaded the Android Studio
Install Android Studio
Open Android Studio after installation.
You will get a dialog box to import settings if you already have Intellij installed on your machine. Say "Do not Import". Otherwise continue to next step.
It will ask you in the dialog box to pre-configure such as theme, path etc.
Just click next next...and then Finish. You will see the SDK tool will start downloading.
After installation is finished. You can find it in this path: C:\Users\<user name>\AppData\Local\Android\sdk
If you have ever installed Android Studio before and then removed it, it won't reinstall the SDK automatically (speculation: some Windows setting somewhere).
The solution is starting Android Studio and then
File -> Manage IDE Settings -> Restore Default Settings
This will wipe any custom settings you don't have at this point and trigger the SDK install
What Pablo wrote is misleading.
This is the "complete" (false!) tool I have just downloaded:
android-studio-ide-171.4443003-windows.exe (SDK is missing here, note
the "ide" in the file name).
Yes, it is IDE only, but after you install this IDE and first time run it, SDK will be downloaded automatically. So there is no need to download some outdated bundles. Just use default "green button" on https://developer.android.com/studio/index.html
I'm using Ubuntu, and had previously installed Android Studio. It was using too much space, so I deleted it. Now when I downloaded it and started ./studio.sh, it found my previous installation configuration directory and asked to import from there. I did, and then this problem occurred.
I put the directory .Android Studio 3.3 in the trash and restarted ./studio.sh, and it imported the SDK automatically for me. That was good, because I couldn't find it where it was supposed to be according to the dialog box. The 3.3 above is from the version of Android Studio I was installing.
in my case, my country is forbidden from google, and my PC's time zone was set by my counrty.
after I change my timezone to another country my problem solved and android studio download SDK and nkd easily
Re-install studio. If ANDROID_HOME is set to custom location then it will install sdk there else it will install SDK in C:\Users<user name>\AppData\Local\Android\sdk
Note:this is a temporary fix
If you have Eclipse then you can use that SDK for emulation.
Just run the sdk manager and emulate a version of android. Then while you are asking for emulating something ie while running code it will show your emulator as online and you can even use it.
Hope this helps you.
All the Best...
This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200
I have recently installed Android SDK on my computer running Windows 7 x64.
I then installed the Eclipse ADT plugin. I am running Eclipse Juno JEE.
When I attempt to run the SDK Manager through Eclipse, I receive the following errors:
Nothing I have tried has allowed me to download/install/update Android SDK and its packages.
I have tried https and forcing http
I have tried running calling program as administrator.
I have added Eclipse, SDK Manager to Firewall exceptions.
I have turned off my antivirus.
I have turned off my firewall.
I have tried various combinations of the above.
I can navigate my browser to both URLs (using Firefox). That should negate "Failed to read..." options 1 and 2. Option 3 seems to be the likely candidate as the XML files do not, in fact, include the <'xsd:schema'> tag. However, I don't know how, if, or where I might be able to point SDK Manager to a local, modified copy of these XML files, or if that would even solve anything.
Any help would be greatly appreciated.
Note: I have installed Android SDK/ Eclipse ADT Plugin on the same machine in the past. This is a fresh install after a recent reimage.
I am not sure if this answer's your question exactly to the point but yet I hope this helps you.
As u wrote it looks like you have downloaded eclipse from its website and android sdk separately from Android website. Why don't you download the Android SDK ADT package with pre-eclipse setup.
That will make your job way lot easier.
The file name would be something like this:
adt-bundle-windows-x86_64-20130729.zip