1991

I am using Eclipse Android plugins to build a project, but I am getting this error in the console window:

[2010-02-03 10:31:14 - androidVNC]Error generating final archive:
Debug certificate expired on 1/30/10 2:35 PM!

How do I fix it?

Improve this question
3
  • 8
    Can someone tell why does this happen?
    – Matical
    Jun 19, 2013 at 17:36
  • 2
    Does your system date changed, cause its of 25 year valid certificate(as recommended while signing application). its not event more than 5 year old specifically
    – Trikaldarshiii
    Jul 25, 2013 at 3:58
  • You need to create new keystore
    – codezoner
    May 19, 2015 at 3:57

18 Answers 18

Reset to default
2272
+50

Delete your debug certificate under ~/.android/debug.keystore on Linux and Mac OS X; the directory is something like %USERPROFILE%/.androidon Windows.

The Eclipse plugin should then generate a new certificate when you next try to build a debug package. You may need to clean and then build to generate the certificate.

Improve this answer
25
  • 13
    On Windows I had to delete the debug.keystore and make some changes to get a new compile going. I created a new test project, and the new debug.keystore was generated.
    – Tomas
    Jun 8, 2010 at 13:37
  • 117
    It will also be re-generated for the current project if you 'clean' the project (go to Project -> Clean...)
    – adamnfish
    Jul 24, 2010 at 17:50
  • 11
    There is now a bug tracker issue requesting this to be fixed. Please vote for it. code.google.com/p/android/issues/detail?id=15370
    – Manfred Moser
    Mar 9, 2011 at 19:52
  • 61
    Clean did not fix the problem for me, I needed to rm ~/.android/debug.keystore by hand.
    – James Moore
    May 2, 2011 at 18:26
  • 3
    @James Deleting the keystore by hand is the first part of the answer above. Cleaning the project (or rebuilding) is what you need to do to generate a new keystore.
    – Christopher Orr
    May 3, 2011 at 22:11
341

Upon installation, the Android SDK generates a debug signing certificate for you in a keystore called debug.keystore. The Eclipse plug-in uses this certificate to sign each application build that is generated.

Unfortunately a debug certificate is only valid for 365 days. To generate a new one you must delete the existing debug.keystore file. Its location is platform dependent - you can find it in Preferences - Android - Build - Default debug keystore.

Improve this answer
4
  • 23
    A change to make the default 30 years was accepted on 6 Apr 2011: review.source.android.com/#change,22128
    – James Moore
    May 2, 2011 at 18:55
  • If you delete your debug.keystore, how would you update your application?
    – user739375
    Jul 21, 2011 at 8:39
  • 6
    @user739375, the debug.keystore is only used for debugging, a separate certificate is used for "production".
    – Teo Klestrup Röijezon
    Jan 1, 2012 at 1:43
  • @JamesMoore I really astonished that how old the certificate was
    – Trikaldarshiii
    Jul 25, 2013 at 4:02
265

It's a pain to have to delete all your development .apk files, because the new certificate doesn't match so you can't upgrade them in all your AVDs. You have to get another development MAP-API key as well. There's another solution.

You can create your own debug certificate in debug.keystore with whatever expiration you want. Do this in the .android folder under your HOME directory:

keytool -genkey -v -keystore debug.keystore -alias androiddebugkey -storepass android -keypass android -keyalg RSA -validity 14000

keytool.exe can be found in the JDK bin folder (e.g. C:\Program Files\Java\jdk1.6.0_31\bin\ on Windows).

ADT sets the first and last name on the certificate as "Android Debug", the organizational unit as "Android" and the two-letter country code as "US". You can leave the organization, city, and state values as "Unknown". This example uses a validity of 14000 days. You can use whatever value you like.

Improve this answer
6
  • 3
    I like this because it provides a more long-term fix until the SDK provides a better way to handle the expiring cert.
    – Sean Aitken
    Apr 5, 2011 at 16:36
  • 24
    I like this because I don't need to use eclipse at all.
    – MattK
    Jun 30, 2011 at 1:50
  • I'm assuming that this is to be typed under the command line. If so, I get a "keytool is not recognized" error. Can you further explain this method?
    – Ted Betz
    Nov 18, 2011 at 19:17
  • 1
    keytool can be found in your JDK's bin directory (any OS). I usually add this bin directory to my PATH so the above would work from anywhere. You could either find your JDK bin directory and add it to your PATH, or you could put the full pathname to keytool on the command line.
    – Dave MacLean
    Nov 26, 2011 at 20:55
  • 1
    As other commenters have pointed out, Google seems to have extended the default duration of the debug certificate so deleting the debug.keystore file and doing clean/build is much easier.
    – Dave MacLean
    Nov 26, 2011 at 21:06
82

On Vista, this worked:

  1. DOS: del c:\user\dad\.android\debug.keystore

  2. ECLIPSE: In Project, Clean the project. Close Eclipse. Re-open Eclipse.

  3. ECLIPSE: Start the Emulator. Remove the Application from the emulator.

You are good to go.

I was pretty worried when I say that error, but I fixed it from reading here and playing around for 10 minutes.

Improve this answer
0
70
  • WINDOWS

Delete: debug.keystore located in C:\Documents and Settings\\[user]\.android, Clean and build your project.

  • Windows 7 go to C:\Users\[username]\.android and delete debug.keystore file.

Clean and build your project.

  • MAC

Delete your keystore located in ~/.android/debug.keystore Clean and build your project.

In all the options if you can´t get the new debug.keystore just restart eclipse.

Improve this answer
58

In Windows 7 it is at the path

C:\Users\[username]\.android
  • goto this path and remove debug.keystore
  • clean and build your project.
Improve this answer
42

If a certificate expires in the middle of project debugging, you must do a manual uninstall:

Please execute adb uninstall <package_name> in a shell.

Improve this answer
0
40

On a Mac, open the Terminal (current user's directory should open), cd ".android" ("ls" to validate debug.keystore is there). Finally "rm debug.keystore" to remove the file.

Improve this answer
0
37

The Android SDK generates a "debug" signing certificate for you in a keystore called debug.keystore.The Eclipse plug-in uses this certificate to sign each application build that is generated.

Unfortunately a debug certificate is only valid for 365 days. To generate a new one, you must delete the existing debug.keystore file. Its location is platform dependent - you can find it in Preferences -> Android -> Build -> *Default debug keystore.

If you are using Windows, follow the steps below.

DOS: del c:\user\dad.android\debug.keystore

Eclipse: In Project, Clean the project. Close Eclipse. Re-open Eclipse.

Eclipse: Start the Emulator. Remove the Application from the emulator.

If you are using Linux or Mac, follow the steps below.

Manually delete debug.keystore from the .android folder.

You can find the .android folder like this: home/username/.android

Note: the default .android file will be hidden.

So click on the places menu. Under select home folder. Under click on view, under click show hidden files and then the .android folder will be visible.

Delete debug.keystore from the .android folder.

Then clean your project. Now Android will generate a new .android folder file.

Improve this answer
35

I had this problem couple of weeks ago. I first tried the troubleshooting on the Android developer site, but without luck. After that I reinstalled the Android SDK, which solved my problem.

Improve this answer
0
34

H-m-m-m. Interesting how so many people have had slightly different experiences with this. I remember the days when this was considered a sign that the software was not ready for release, and the team would actually fix it BEFORE users started seeing these problems:(

My own experience was just a little different. I had already tried Project>Clean, but still got the same build failure. Then I deleted the debug.keystore (under .android) just as the first answer said. Still got the same problem. Then I did a clean again, and wonder of wonders, it worked!

Now don't get me wrong, I am glad that I got it working thanks to the hints in this thread. But clearly clean isn't working right, and how did it find an expired key after I deleted the keystore??? Clearly something is wrong with Eclipse or the ADT -- not so sure which.

Improve this answer
1
  • Eclipse tends to cache files, so a clean/refresh is required sometimes to let it know that the file has changed on disk.
    – navjotk
    Apr 3, 2012 at 15:08
34

On Ubuntu, this worked:

I went to home/username/.android and I renamed keystore.debug to keystoreold.debug. I then closed Eclipse, started Eclipse, and SDK created new certificate keystore.debug in that folder.

You then have to uninstall/reinstall apps you installed via USB Debugging or an unsigned APK ("unsigned" APK = signed with debug certificate).

Improve this answer
15

First close the eclipse then

Open CMD by Window Key + R or via Run as Admin

Follows the following step

del "%USERPROFILE%\.android\debug.keystore"
keytool -genkey -v -keystore "%USERPROFILE%\.android\debug.keystore" -alias androiddebugkey -storepass android -keypass android -keyalg RSA -validity 30000

after this restart eclipse.

Improve this answer
15

For windows xp go to C:\Documents and Settings\%userprofile%\.android and delete debug.keystore file, restart the eclipse and now your project get build without error.

Example path:

C:\Documents and Settings\raja.ap\.android\

read-here-for-more.

Improve this answer
0
14

In Windows debug.keystore file is localtes at C:\Users\%Username%\.android folder. This file is created when you install your android SDK and is valid only for a year. After this perod you will start getting this error Error getting final archive: Debug certificate expired on xx/xx/xxxx.

To remove this error simply delete the file and run the program again. In my Eclipse I have enabled Project->Build Automatically so it directly worked but in case you have disabled it you will need to clean the project Project->Clean.. select your project and press ok. Then you will need to build it manually. 3rd click on your project and select Build project.(Note - You will only see this option if you have diabled Build Automatically feature in your Projects Menu)

Improve this answer
8

After you install the Android SDK in Eclipse, it generates a debug signing certificate for you in a keystore called debug.keystore. The Eclipse plug-in uses this certificate to sign each application build that is generated.

Now, the problem with this debug certificate is that it is only valid for a year, or 365 days. If your Eclipse IDE uses an expired debug certificate, you will not be able to create and/or deploy an Android app.

To fix this problem all you need to do is delete the debug.keystore file.

  1. Go to Preferences
  2. Android
  3. Build
  4. Default debug keystore

There you should see the folder where the file is located. Simply delete that file and you are good to go.

For more info. you can visit

http://developer.android.com/tools/publishing/app-signing.html

Improve this answer
2

To fix this problem, simply delete the debug.keystore file.

The default storage location for AVDs is

In ~/.android/ on OS X and Linux.

In C:\Documents and Settings\.android\ on Windows XP

In C:\Users\.android\ on Windows Vista and Windows 7.

Also see this link, which can be helpful.

http://developer.android.com/tools/publishing/app-signing.html

Improve this answer
0

Delete the debug.keystore located at C:\Users\%Username%\.android folder. Then run the app. It will generate the new one.

Improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.