Android Debug Key Expired? So Did Your Debug Maps API Key!

As an Android developer, you've probably run into an expired debug key by now. If you use the Maps API, you'll inevitably run across the other issue: your maps key is tied to your debug certificate and it also stops working. This happened to me because of a lengthy break from use the Maps API. My old code had a Maps API key in it tied to an equally old debug key. Naturally, using the new debug key meant this didn't work at all.

Now, if you've followed our advice and created a certificate that won't expire for a long, long time, then you can create a debug maps key that will work with it for a long, long time.

It's all pretty simple:

First, create your new debug.keystore file, using all the mandatory values:

keytool -genkey -keypass android -keystore debug.keystore -alias androiddebugkey -storepass android -validity 10000 -dname "CN=Android Debug,O=Android,C=US"

Next, get the certificate fingerprint for use in generating the Maps API key:

keytool -list -keystore debug.keystore -storepass android

Like so:

Command results for keytool

Finally, use that to generate your new Maps API Key. The results will look like this:

After generating new Maps API Key

If your debug.keystore file is now stored in a non-standard location, don't forget to update your build tools. In Eclipse preferences, this is the screen that needs to change:

Edit the path to your debug.keystore file

Not a Programmer? You Can Still Create Android Apps!

Google has introduced a new tool today called App Inventor. It uses the Open Blocks Java library to allow visual creation of applications, online.

This could be useful for regular developers to prototype quick apps. But, the real use is for non-developers or young folks. What would your kid create if they could create something with no coding required? Might it be silly? Might it be something other kids would have fun with? If you're not a developer, what would you create?

The tool, as it stands now, isn't fully open to the public. You have to fill out a form and then Google will eventually add access. The form is definitely aimed at educators. It's clear Google is looking at this as a teaching tool of sorts. We've always thought mobile programming would make a great target for teaching. This is evidence we aren't alone in that thought.

Sam's Teach Yourself Android Application Development in 24 Hours NOW AVAILABLE!

Our new book, Sam's Teach Yourself Android Application Development in 24 Hours, is now IN STOCK at Amazon! You might even have it already if you pre-ordered it. ;)


Remember, this is a full color book. Figures are color, code is syntax-highlighted. Color and a lower price? How do they do that? Anyway, it's more beginner oriented than our first book, Android Wireless Application Development, but it also covers some new topics. We're underway on an update to our first book, too.

Our New Android Book Printed!

We just got our first copy of Sam's Teach Yourself Android Application Development in 24 Hours in both print form and "folded and gathered" form. (That's for us to make corrections on, but it's kind of neat.) It's still pre-order on Amazon, but it should be available pretty soon! So, don't forget to pre-order and be amongst the first to get one. :)

It's a full-color book, too. The code samples are color coded which, to us, makes them far easier to read. Images are easier to view, too.

Don't Mess with Android!

Korean operator SK Telecom has created what we think are the best series of Android commercials to date. Enjoy!
















Rawr! Korean Android is Spunky!

Working with the Android Calendar

Last December, we wrote an article at developer.com about how to use the undocumented Android Calendar content provider. At the time, we'd written the code for Android SDK 1.6. Numerous updates later, this code still worked on Android 2.1. Now, however, Android SDK 2.2 finally broke it. Interestingly, the fixes were rather straight forward, though.

Instead of trying to update the article, write a new one, or try to post all the changes somewhere, we've decided to open source the code so others can see it and, if they'd like, contribute to it. The idea of the code is to demonstrate how to use the calendar content provider. Right now, it shows how to add, edit, and delete a basic entry as well as read the contents. If you'd like to see more, why not contribute to the code so others can see more to?

This uses an undocumented content provider. As it has changed, it may continue to change. The use of this code is at your own risk. Any damage it does is not our fault. You've been warned.

We also don't necessarily recommend this method of controlling a user's calendar. It interfaces with Google Calendars, which has an API of its own that is well documented and can perform everything needed. This avoids any complications with the Android client, will work even if the devices doesn't have a calendar (a non-Google Android device, for instance), and its documented. :)

In any case, we've tested the current code on our Nexus One with Android 2.2 and our Evo 4G with Android 2.1-update1. It works, but it may not work on your devices. Use with care.

Book Updates

Our upcoming book, Sam's Teach Yourself Android Application Development in 24 Hours, is finally done with the editing process. This means it's heading off to the printers and will be on shelves in due time. (This is not the quickest of processes; those darned real world items! Be patient, but don't forget to pre-order to be first on the block.)

Generally, the downloadable code is made available only to folks who have purchased the print copy. However, due to popular demand, our publisher has made available the downloads as part of the Rough Cuts program. If you have access to Rough Cuts via Safari, the downloads are now available! Enjoy.

Finally, have we mentioned that there's another book in the pipeline?