If an attempt is made to upload another APK file with the same version code number, the console will reject the file with the following error: You need to use a different version code for your APK because you already have one with version code 1. The first APK file uploaded for your application will invariably have a version code of 1. Uploading New APK Versions to the Google Play Developer Console Having collected the above information and prepared the application package file for release, simply follow the steps in the Google Play Developer Console to submit the application for testing and sale. Pricing & Distribution – Information about the price of the application and the geographical locations where it is to be marketed and sold.Contact Information – Methods by which users may contact you for support relating to the application.Locations – The geographical locations into which you wish your application to be made available for purchase.Category – The category that best describes your application (for example finance, health and fitness, education, sports etc.).Application Type – Whether your application is considered to be a game or an application.Promotional Text – The text that will be used when your application appears in special promotional features within the Google Play environment.Language – The language of the application (the default is US English).Google recommends submitted screenshots of the application running on a 7” or 10” tablet. Screenshots – Up to 8 screenshots of your application running (a minimum of two is required). Description – Up to 4000 words describing the application.In order to bring your application to market, the following information will be required: Once the account has been created, the next step is to gather together information about the application. Once an application goes on sale, Google will keep 30% of all revenues associated with the application. Note that there is a one-time $25 fee to register. To do so, navigate to and follow the instructions to complete the registration process. The first step in the application submission process is to create a Google Play Developer Console account. Register for a Google Play Developer Console Account Once submitted, the application will be available for download from the Google Play App Store. The final step in the process of bringing an Android application to market involves submitting it to the Google Play Developer Console. The private key generated as part of this process should be used when signing and releasing future applications and, as such, should be kept in a safe place and securely backed up. Once the build is complete, a dialog will appear providing the option to open the folder containing the APK file in an explorer window:Īt this point the application is ready to be submitted to the Google Play store. At this point the Gradle system will compile the application in release mode. In the event that another location is preferred, click on the button to the right of the text field and navigate to the desired file system location.Įnable the Run ProGuard checkbox (ProGuard performs a series of optimization and verification tasks that result in smaller and more efficient byte code) before clicking on the Finish button. Within this screen, review the Destination APK path: setting to verify that the location into which the APK file will be generated is acceptable. At this point the Generate Signed APK Wizard dialog should still be displayed with the keystore path, passwords and key alias fields populated with information:Īssuming that the settings are correct, click on the Next button to proceed to the APK generation screen (Figure 54-7). The next task to be performed is to instruct Android Studio to build the application APK package file in release mode and then sign it with the newly created private key. The lower section of the dialog relates to the release key that will be stored in the key store file. In this section, enter a strong password with which to protect the keystore file into both the Password and Confirm fields. The top section relates to the keystore file. The New Key Store dialog is now divided into two sections. Click on the button to the right of the Key store path field and navigate to a suitable location on your file system, enter a name for the keystore file (for example ) and click on the OK button. In the event that you have yet to create a keystore file, click on the Create new… button to display the New Key Store dialog (Figure 54-4). In the event that you have an existing release keystore file, click on the Choose existing… button and navigate to and select the file. To create a keystore file, select the Build -> Generate Signed APK… menu option to display the Generate Signed APK Wizard dialog as shown in Figure 54-3:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |