Here are some tips and tricks for common Android errors. Don't forget to use the
ddms logcat capability to get a deeper view when errors occur. See Debugging for more debugging tips.
ADT Installation Error: "requires plug-in org.eclipse.wst.sse.ui".
The "Android Editors" feature of the ADT Plugin requires specific Eclipse components, such as WST. If you
encounter this error message during ADT installation, you need to install the
required Eclipse components and then try the ADT installation again. Follow the steps below to install the required components for the
Android Editors feature, based on the version of Eclipse that you are using.
| Eclipse 3.3 (Europa) | Eclipse 3.4 (Ganymede) |
|---|
- From the dialog where you select the Update sites to visit, select the checkboxes for both the
ADT site, and the Callisto/Europa/Ganymede Discovery Site (you may want to
check Automatically select mirrors at the bottom).
- Click Finish.
- In the Next dialog, select the Android Plugins.
- Now, expand the tree item of the discovery site. It seems that if you
don't do it, it doesn't load the content of the discovery site.
- On the right, click Select required. This will select all the components
that are required to install the Android plugin (wst, emf, etc...).
- Click Next, accept the agreement, click Install All, and restart Eclipse.
|
- Select Help > Software Updates...
- Select the Installed Software tab.
- Click Update...
- If an update for ADT is available, select it and click Finish.
|
ADB reports "no device" when an emulator is running
Try restarting adb by stopping it (adb
kill-server) then any other adb command to restart it.
My new application/activity isn't showing up in the
applications list
- You often must restart your device or emulator before a new activity shows
up in the applications list. This is particularly true when it is a completely
new application with a new AndroidManifest.xml file.
- If this is for a new activity in an existing AndroidManifest.xml file, did
you include an
<activity> tag for your app (or a <service> tag
for a service, or a <receiver> tag for a receiver, etc.)?
- Make sure that your AndroidManifest.xml file is valid. Errors in attribute
values, such as the value attribute in
<action value="<something>">
will often not be caught by compilers, but will prevent your application
from being displayed because the intent filter will not be matched. Extra
spaces or other characters can often sneak into these strings.
- Did you send your .apk file to the device (adb install)?
- Run logcat on your device (
adb logcat)
and then install your .apk file. Check the logcat output to see whether the
application is being installed and recognized properly. Here's sample output
from a successful installation:
I/FileObserver( 414): *** onEvent wfd: 3 mask: 8 path: MyRSSReader.apk
D/PackageManager( 414): Scanning package: /data/app/MyRSSReader.apk
D/PackageManager( 414): Adding package com.example.codelab.rssexample
D/PackageManager( 414): Registered content provider: my_rss_item, className = com.example.codelab.rssexample.RssContentProvider, isSyncable = false
D/PackageManager( 414): Providers: com.example.codelab.rssexample.RssContentProvider
D/PackageManager( 414): Activities: com.example.codelab.rssexample.MyRssReader com.example.codelab.rssexample.MyRssReader2
- If logcat shows that the package manager is having problems loading the manifest
file, force your manifest to be recompiled by adding a space in the file and
compiling it.
I updated my app, but the updates don't seem to be showing up on the device
Did you remember to send your .apk file to the device (adb
install)?
I'm getting a "Binary XML file line #2: You must supply a layout_wilih
attribute" error
when I start an application (but I declare a layout_wilih attribute right
there!!!)
- Make sure that the SDK you are building with is the same version as the Android
OS that you are running on.
- Make sure that you're calling setContentView() early in your onCreate() method.
Calling other methods, such as setListAdapter() before calling setContentView()
can sometimes create odd errors when Android tries to access screen elements
that haven't been set before.
My request to (make a call, catch an incoming SMS,
receive a notification, send an intent to an Android application) is being
ignored
You might not have permission (or might not have requested permission) to
call this activity or receive this intent. Many standard Android activities,
such as making a call, have a permission assigned to it to prevent arbitrary
applications from sending or receiving requests. See Security and
Permissions for more information on permissions, and
Manifest.permission for a list of
standard permissions supported by the Android platform.
Help! My project won't build in Eclipse
If your project doesn't build, you may notice symptoms such as new
resources added in the res/ sub-folders not showing up in the R class,
the emulator not being started, not being able to run the application, or even seeming to run an old version of the application.
To troubleshoot these types of problems, first try:
- Switch to the DDMS view in Eclipse (if you don't already have it open):
- From the menu select
Window > Open Perspective > Other
- Select DDMS from the list and hit OK
- In the Devices panel (top right panel by default), click on the down triangle
to bring up the panel menu
- Select
Reset ADB from the menu, and then try running the
application again
If the above still doesn't work, you can try these steps:
-
Check the console and problems tabs at the bottom of the Eclipse UI
-
If there are problems listed in either place, they should give you a clue
what is wrong
-
If you aren't sure if the problems are fresh or stale, clear the console
with a right click > Clear, then clean the project
-
To clean the project (a good idea with any kind of build error), select
Project > Clean from the eclipse main menu, then select the project you
are working on (or clean all)
Eclipse isn't talking to the emulator
When communication doesn't seem to be happening between Eclipse and the emulator, symptoms can include: nothing happening when you press run, the emulator hanging waiting
for a debugger to connect, or errors that Eclipse reports about not being able
to find the emulator or shell. By far the most common symptom is that when you press run, the emulator starts (or
is already running), but the application doesn't start.
You may find any of these steps will fix the problem and with practice you
probably can figure out which one you need to do for your particular issue, but
to start with, the safest option is to run through all of them in order:
-
Quit the emulator if it is running
-
Check that any emulator processes are killed (sometimes they can hang, use ps on unix or mac, or task manager in the process view on
windows).
-
Quit Eclipse
-
From the command line, type:
adb kill-server
-
Start Eclipse and try again
When I go to preferences in Eclipse and select "Android", I get the following error message: Unsupported major.minor version 49.0.
This error is displayed if you are using an older version of the JDK. Please make sure you are using JDK version 5 or 6.
I can't install ApiDemos apps in my IDE because of a signing error
The Android system requires that all applications be signed, as described in
Signing Your Applications. The ApiDemos
applications included with the SDK are preinstalled on the emulator and for that reason have been
compiled and signed with a private key.
If you want to modify or run one of the ApiDemos apps from Eclipse/ADT or other IDE, you can do so
so only after you uninstall the
preinstalled version of the app from the emulator. If
you try to run an ApiDemos apps from your IDE without removing the preinstalled version first,
you will get errors similar to:
[2008-08-13 15:14:15 - ApiDemos] Re-installation failed due to different application signatures.
[2008-08-13 15:14:15 - ApiDemos] You must perform a full uninstall of the application. WARNING: ...This will remove the application data!
[2008-08-13 15:14:15 - ApiDemos] Please execute 'adb uninstall com.android.samples' in a shell.
The error occurs because, in this case, you are attempting to install another copy of ApiDemos
onto the emulator, a copy that is signed with a different certificate (the Android IDE tools will
have signed the app with a debug certificate, where the existing version was already signed with
a private certificate). The system does not allow this type of reinstallation.
To resolve the issue, you need to fully uninstall the preinstalled and then reinstall it using
the adb tool. Here's how to do that:
- In a terminal, change to the tools directory of the SDK.
- If no emulator instance is running, start an emulator using using the command
emulator &.
- Uninstall the preinstalled app using the command
adb uninstall com.android.samples.
- Reinstall the app using the command
adb install <path to the ApiDemos.apk>. If you are
working in Eclipse/ADT, you can just compile and run the app in the normal way.
Note that if multiple emulator instances are running, you need to direct your uninstall/install
commands to the emulator instance that you are targeting. To do that you can add the
-s <serialNumber> to the command, for example:
adb -s emulator-5556 install
For more information about adb, see the Android Debug Bridge
documentation.
I can't compile my app because the build tools generated an expired debug certificate
If your development machine uses a locale that has a non-Gregorian calendar, you may encounter problems when first trying to compile and run your application. Specifically, you may find that the Android build tools won't compile your application because the debug key is expired.
The problem occurs because the Keytool utility — included in the JDK and used by the Android build tools — fails to properly handle non-Gregorian locales and may create validity dates that are in the past. That is, it may generate a debug key that is already expired, which results in the compile error.
If you encounter this problem, follow these steps to work around it:
- First, delete the debug keystore/key already generated by the Android build tools. Specifically, delete the
debug.keystore file. On Linux/Mac OSX, the file is stored in ~/.android. On Windows XP, the file is stored in
C:\Documents and Settings\<user>\.android. On Windows Vista, the file is stored in
C:\Users\<user>\.android
- Next, you can either
- Temporarily change your development machine's locale (date and time) to one that uses a Gregorian calendar, for example, United States. Once the locale is changed, use the Android build tools to compile and install your app. The build tools will regenerate a new keystore and debug key with valid dates. Once the new debug key is generated, you can reset your development machine to the original locale.
- Alternatively, if you do not want to change your machine's locale settings, you can generate the keystore/key on any machine using the Gregorian calendar, then copy the
debug.keystore file from that computer to the proper location on your development machine.
This problem has been verified on Windows and may apply to other platforms.
For general information about signing Android applications, see
Signing Your Applications.
