Inicio / Información general / Updating existing applications

Updating existing applications

Actualizado el 09 de julio de 2026
Este artículo aún no está disponible en Español. Se muestra la versión en English.

Updating existing applications

If your company already has mobile applications published on the Apple and Google stores and wishes to update them with the Chargekeeper solution, please follow the steps and conditions below.

Chargekeeper email address: connection@charge-keeper.com

 

1. Access to Store accounts

Before any update, it is mandatory to invite the Chargekeeper team as an administrator on:

  • the Apple App Store account
  • the Google Play Console account

 

2. Android-specific case – Application signing

For Android, the ability to update an existing application depends on the initial signing method.

2.1 Checking the signing file (keystore)

  • Check with your previous partner whether they have a signing file called a keystore
  • This file:
    • is unique and cannot be regenerated
    • is associated with:
      • a password
      • an alias name
  • These elements must be retrieved and stored securely in your company's information system

Without this file, it is impossible to update the application via a local signature.

 

2.2 The Play App Signing case (Google Play)

If you do not have the keystore file, the application may have been signed via the Play Store using the Play App Signing service.

To check this:

  • Go to the application's page in the Google Play Console
  • Click on App Integrity
  • Check whether the App signing by Google Play service is enabled

👉 This check can be carried out by Chargekeeper once the connection team has been invited to your Google Play account.

 

3. Migration of user accounts – Important information

When migrating an existing application to the Chargekeeper mobile application, the user accounts from the old application may not be retained.

Main reasons:

  • Passwords are generally encrypted (security, GDPR compliance) and cannot be recovered
  • The data structures between the two applications may differ, preventing a direct migration

 

4. Cases where a migration of users is feasible

If the previous platform allows exporting user accounts:

  • The client provides an export of the users in a standard format:
    • SQL, CSV, XLS/XLSX or JSON (compressed if necessary)
  • Chargekeeper analyses the technical feasibility
    • If migration is possible: the cost and lead time will be assessed based on the workload

 

5. Chargekeeper recommendation

In order to ensure a smooth and secure transition, Chargekeeper recommends by default:
👉 the creation of new user accounts in the new application.