Preparing the app for distribution
Video: Preparing the app for distributionWhen your Android app is finished and ready for distribution, you'll need to export it so that it can be added to the Google Play store, or otherwise distributed to your users. When you export it for general use, you'll use a different key store then you used during development. You'll use a certificate that you generate either from eclispe or from the command line. This new key store will have a different SHA1 fingerprint then your debug key store and that fingerprint must be registered with the Google API's console.
- Next steps
Viewers: in countries Watching now:
Maps make mobile apps more useful; they can help users find businesses and areas of interest, get directions, or gain insights into new communities. In this course, learn to add interactive maps to your Android apps with Google Maps Android API v2. David Gassner first shows you how to set up the tools, get an API key, and import and link to Google Play services. After an introduction to presenting simple maps with the MapView and MapFragment classes, the course describes how to set a map's initial state, switch between different map types, work with map markers, draw shapes, and work with zoom controls, the My Location button, and various user gestures. Finally, learn to add a map to an existing app and prepare it for distribution.
Note: An Android device with Android 3.0 (Honeycomb) or higher, and that has Google Play Store installed, is required to use the course exercises. (Kindle Fire and Nook devices do not qualify.) Finished mapping apps can be deployed on Android 2.2 (Froyo) or later.
- Setting up the developer tools
- Adding required permissions
- Getting a Google Maps API key
- Importing and linking the Google Play services
- Setting a map's initial state
- Geocoding an address
- Getting the current location programmatically
- Adding map markers
- Handling marker events
- Drawing lines, polygons, and circles
- Adding maps to existing apps
Preparing the app for distribution
When your Android app is finished and ready for distribution, you'll need to export it so that it can be added to the Google Play store, or otherwise distributed to your users. When you export it for general use, you'll use a different key store then you used during development. You'll use a certificate that you generate either from eclispe or from the command line. This new key store will have a different SHA1 fingerprint then your debug key store and that fingerprint must be registered with the Google API's console.
I'm working with the version of my project that is not included in the exercise files, its called TourFinder1.0 and this is the version that I'll be uploading to the Google play store. I'll select File > Export, and then under the Android category, I'll choose Export Android Application. I'll choose the project and click Next. And then, I've already created a key store file. After selecting it, I'll type in the key store password.
I'll click, Next. Then I'll select the, Alias and I'll type in that password. And click Next again. On this screen, before you complete the expert operation, you'll see the key store fingerprints, including the SHA1 fingerprint. This is the fingerprint you need to register in the Google API's console. I'll select and copy it, and then, finish the export process. Then I'll go to the Google API's console, and I've selected my project, Explore CA TourFinder. Before I recorded this movie, I'd already gone through this process, and I added the SHA 1 fingerprint for the production certificate to this list.
It's right down here. It starts with the finger print and finishes with the package of the app/g. The other three digital finger prints are for different development computers. This architecture allows you to add multiple development computers, and the apps production certificate to a list. And all those fingerprints point to a single API key. And that's the API key that you add to the Android manifest file, right down here. So those are the last steps you need to follow before you deploy your application.
And then you'll be ready to upload the app to the Google Play store or another Android market or otherwise distribute your app with Google Maps to your users.
Find answers to the most frequently asked questions about Building Mobile Apps with Google Maps Android API v2 .
Here are the FAQs that matched your search "" :
- Q: In the Chapter 2 movie "Checking the device for the Google Play services APK," when I create my first Google Maps app, the app crashes when I call the custom method servicesOK(). The error in LogCat starts with:"java.lang.IllegalStateException: The meta-data tag in your app's AndroidManifest.xml does not have the right value."How do I fix this?
- A: The latest version of the Google Play services library has a new required meta-data tag in the app manifest. Add the following tag within the <application> tag:<meta-data
android:value="@integer/google_play_services_version" />After rebuilding the app, the error should be resolved.
Sorry, there are no matches for your search "" —to search again, type in another word or phrase and click search.