In this tutorial we will explain how to generate the Keystore certificate for the Google Play Store and the .APP file to upload to the store.
In order to produce an APP file for the Play Store, you need to sign it with a Keystore file.
The Keystore file is a certificate that is used to prove that the APP being submitted belongs to you and prevents 3rd parties from submitting an app update to the Play Store even if your Google Play account is compromised.
Now let’s see how to generate the Keystore certificate using our plugin wizard.
To generate the certificate, select the my fastapp setting menu.
Let’s click on the Android Tab. Now we tick the Build for Android enabled check box.
Now let’s click on the start wizard button.
In the screen that appears, fill in the first field with the email we used to create our Google developer account.
In the second field we insert the keystore alias, here we can insert a fantasy name.
After filling in the fields, click on the GENERATE button now you have to wait a few tens of seconds for our servers to process the request.
At the end I remind you to save the changes and in this case you will also have to click on the publish button.
Your certificate has now been generated and automatically loaded into the plugin.
Now you can generate the package which you will then upload to the Google Play Store.
To do this you have to click on the My FastAPP DOWNLOAD BUILDS menu.
Here you see an already present package generated in a previous demonstration.
To create our new build we click on the create build button.
This way the build will be queued on our servers.
This phase can take a few minutes as our servers are creating all the dependencies needed to deploy the build.
in the meantime we can go and check the developer’s email box.
We find an email with the generated certificate data and the link to download it locally.
Attention it is important to keep this data that you will need to eventually update the app.
ATTENTION if you lose them you can no longer modify your APP.
Also you can use this certificate to generate other apps.
A good tip is to have a certificate for every open Google Play Store.
Now let’s go back to our site and check if the build is complete by clicking on the refresh button.
Your build is ready you can click on the download symbol and download it.
Keep in mind that you will receive a zip file so you will have to unzip it and extract the .app file this file will then be uploaded to your Google Play Store.
Teamonair srl Numero REA VE: 433600 P.Iva: 04616720274
Copyright © 2021 – Teamonair srl
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_0QDQ83VGDR | 2 years | This cookie is installed by Google Analytics. |
_gat_gtag_UA_35217179_75 | 1 minute | Set by Google to distinguish users. |
_gat_UA-35217179-75 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
Cookie | Duration | Description |
---|---|---|
__Secure-wp_seraph_accel_sess_m | 1 year | No description |
AnalyticsSyncHistory | 1 month | No description |
li_gc | 5 months 27 days | No description |