How to update an existing Android mobile app with a new Android mobile app built by Lightcast
Overview
This article explains what to do if you already have a published Android mobile app and want Lightcast to update it with the Lightcast app framework.
When to update an existing Android mobile app
Use this information if your organization already has a published Android mobile app before starting a new Android mobile app build with Lightcast.
In most cases, the best option is to update the existing Android mobile app instead of removing it and submitting a brand new app. Updating the existing app helps preserve the app’s current Google Play Store listing, users, and install base.
Before Lightcast can update an existing Android mobile app, you need to determine where the app is currently located:
In your organization’s Google Developer Account
In another developer’s Google Developer Account
In an account you do not currently have access to
As part of your mobile app specs form, you will be asked whether you already have an Android mobile app and whether you want Lightcast to update the existing app or build a new Android mobile app. Your answer helps Lightcast determine the correct next steps.
How it works
Google requires each publisher to have its own Google Developer Account where Android apps can be published and managed.
When Lightcast updates your existing Android mobile app, the app remains under the same Google Play Store listing. This helps preserve the app’s current listing, users, and install base while Lightcast prepares and submits the updated app version through your Google Developer Account.
To update an existing Android mobile app, Lightcast needs access to the Google Developer Account where the app is published. Lightcast also needs the app’s keystore file and password details.
The keystore file is used to sign the Android mobile app. It is required when an existing Android mobile app is updated. The keystore file is usually in .jks or .keystore format.
Lightcast may need the following keystore details:
Keystore file
Keystore file password
Keystore alias
Keystore alias password
If the app is in your Google Developer Account, you can invite Lightcast as an Admin user so our development team can prepare and submit the updated Android mobile app build.
If the app is in another developer’s Google Developer Account, that developer must transfer the app to your Google Developer Account first. After the app is transferred, you can invite Lightcast as an Admin user and provide the required keystore information.
If your organization does not have a Google Developer Account yet, you will need to create one before the app can be transferred to your account.
Removing the existing Android mobile app and submitting a brand new app should only be considered if updating or transferring the existing app is not possible.
Instructions
Follow the scenario that matches where your existing Android mobile app is currently located.
If the app is in your organization’s Google Developer Account
Step 1
Confirm that your organization can access the Google Developer Account where the existing Android mobile app is located.
Step 2
Invite developer@lightcast.com to your Google Developer Account as an Admin user.
For help with this process, see How to create a Google Developer Account for your Android TV or Android mobile app.
Step 3
Send Lightcast the keystore information for the existing Android mobile app.
This may include:
Keystore file
Keystore file password
Keystore alias
Keystore alias password
Step 4
Notify Customer Support after the Admin invitation has been sent and the keystore information has been provided.
Lightcast can then review access and continue preparing the updated Android mobile app build.
If the app is in another developer’s Google Developer Account
Step 1
Create your organization’s own Google Developer Account if you do not already have one.
For help creating your account, see How to create a Google Developer Account for your Android TV or Android mobile app.
Step 2
Ask the current developer to transfer the existing Android mobile app into your organization’s Google Developer Account.
Step 3
Ask the current developer to provide the keystore information for the existing Android mobile app.
This may include:
Keystore file
Keystore file password
Keystore alias
Keystore alias password
Step 4
After the app is transferred, invite developer@lightcast.com to your Google Developer Account as an Admin user.
For help with this process, see How to create a Google Developer Account for your Android TV or Android mobile app.
Step 5
Provide Lightcast with the keystore information for the existing Android mobile app.
Step 6
Notify Customer Support when the app transfer is complete, the Lightcast invitation has been sent, and the keystore information has been provided.
Lightcast can then review access and continue preparing the updated Android mobile app build.
If you are not sure where the app is located
Step 1
Check whether your organization has access to the Google Developer Account where the existing Android mobile app is managed.
Step 2
If you do not have access, contact the person or developer who originally created or submitted the Android mobile app.
Step 3
Ask which Google Developer Account currently manages the app.
Step 4
Ask whether the app can be transferred into your organization’s Google Developer Account.
Step 5
Ask the current developer whether they can provide the keystore file and password details for the existing Android mobile app.
Step 6
Contact Customer Support if you need help determining the next step.
FAQs
Does an existing Android mobile app need to be removed before Lightcast builds a new app?
Usually, no. In most cases, the best option is to update the existing Android mobile app instead of removing it.
Updating the existing app helps preserve the app’s current Google Play Store listing, users, and install base.
Why is updating the existing Android mobile app usually better than removing it?
Updating the existing app helps preserve the app’s current Google Play Store presence.
If the existing app is removed, viewers may lose access to the published app while the new app is built, submitted, reviewed, and approved by Google.
What does Lightcast need to update an existing Android mobile app?
Lightcast needs access to the Google Developer Account where the app is published.
Lightcast also needs the keystore file and password details for the existing Android mobile app. This may include the keystore file, keystore file password, keystore alias, and keystore alias password.
What is a keystore file?
A keystore file is used to sign the Android mobile app.
If Lightcast is updating an existing Android mobile app, the keystore file used for the existing app is required so the updated app can be submitted correctly.
What happens if the keystore information is not available?
The keystore information is required to update the existing Android mobile app.
If the keystore information is not available, Lightcast may not be able to update the existing app. In this case, the Android mobile app would need to be submitted to the Google Play Store as a new app.
What should be done if the existing Android mobile app is in your organization’s Google Developer Account?
Invite developer@lightcast.com as an Admin user in your Google Developer Account.
Then provide the keystore information for the existing Android mobile app and notify Customer Support so Lightcast can continue preparing the updated app build.
What should be done if the existing Android mobile app is in another developer’s Google Developer Account?
Work with the current developer to transfer the existing Android mobile app into your organization’s Google Developer Account.
You should also ask the current developer to provide the keystore file and password details for the existing app. After the app is transferred, invite developer@lightcast.com as an Admin user so Lightcast can update the app.
What if your organization does not have a Google Developer Account yet?
Create a Google Developer Account for your organization first.
After the account is created and approved by Google, the current developer can transfer the existing Android mobile app into your Google Developer Account.
Can an existing Android mobile app be transferred directly to Lightcast’s Google Developer Account?
No. Google requires each publisher to have its own Google Developer Account where apps can be published and managed.
Lightcast can update your existing Android mobile app from your organization’s Google Developer Account after Admin access is granted and the required keystore information is provided.
Can Lightcast build a brand new Android mobile app instead of updating the existing app?
Yes. Lightcast can develop and submit a brand new Android mobile app if you do not want to update the existing app or if updating the existing app is not possible.
A new app will not preserve the existing app’s users, install base, or Google Play Store listing.
