Transferring an Android TWA App Between Google Play Accounts

Transferring ownership of an Android application between Google Play Developer accounts is a routine operational task. This process occurs during corporate acquisitions, business restructurings, agency-to-client handoffs, or when transitioning from an individual account to an organisation account. However, for applications built using a Trusted Web Activity (TWA), an app transfer introduces unique technical considerations. Because TWAs are tightly coupled with web domains via Digital Asset Links, a failure to handle the transfer correctly can result in broken app installations and unexpected URL bars for your users.

The Core Technical Mechanics of a TWA Transfer

When you transfer a standard native application, Google Play handles the migration of the package name, the rating history, the user reviews, and the active install base. The underlying app signing key managed by Google Play App Signing is also transferred seamlessly to the target developer account. For a TWA, these elements are equally preserved. However, the connection between the Android application and your web domain is governed by the assetlinks.json file hosted on your web server.

To ensure a seamless transition where users do not experience any disruption, you must verify that the target developer account has the capacity to maintain the app signing chain, and that the associated web domains remain aligned with the app package. A failure to coordinate the transfer with domain control will cause the TWA to lose its verified status, falling back to a standard browser-wrapped experience displaying the top address bar.

Pre-requisites for Initiating the Transfer

Before submitting an app transfer request in the Google Play Console, you must gather specific information from both the source (transferor) and target (transferee) developer accounts. Note that Google Play requires a one-off 25 USD developer registration fee for the target account if it is brand new. The following checklist details the items required to ensure a successful administrative transfer:

To find the registration transaction ID, search the email inbox associated with each Google Play account for the payment receipt received when paying the 25 USD developer registration fee. The transaction ID typically formatted as GPA.XXXX-XXXX-XXXX-XXXXX or 01234567890123456789.token.GPB.XXXXXXXXXXXX is mandatory for Google to validate the transfer request.

Step-by-Step TWA Transfer Process

Once all preparation is complete, follow these sequential steps to execute the transfer and maintain complete technical continuity.

Step 1: Check Google Play App Signing Status

Verify that your TWA is enrolled in Google Play App Signing in the source account. If it is, Google holds the master app signing key. This is the optimal configuration, as Google will automatically transfer this key to the target developer account. If you are using a legacy manual signing method where you manage the keystore yourself, you must securely package and deliver the private keystore file (.jks), the key alias, and all associated passwords to the target developer. Without this keystore, the new owner will never be able to publish updates to your application.

Step 2: Submit the Transfer Request

The owner of the source account must log into the Google Play Console, navigate to the Setup section, and select App Transfer. Click on the Transfer App button. Enter the email address of the target account owner and the target Developer Account ID. You will also need to enter the original registration transaction ID for the source account and explain the reason for the transfer. Submit the request.

Step 3: Accept the Transfer Request

The owner of the target developer account will receive an email notification and a notification within their Google Play Console dashboard. They must review and accept the transfer terms. This includes confirming compliance with all Google Play developer policies and agreeing to maintain the existing application guidelines.

Step 4: Audit the Digital Asset Links Post-Transfer

Once Google processes the transfer (which typically takes anywhere from a few hours up to several business days), the app will appear in the target developer console. At this point, you must audit your Digital Asset Links immediately. Because Google Play App Signing transfers the exact same signing key, the SHA-256 fingerprint of the production application remains unchanged. This means that if the domain ownership has not changed, your existing assetlinks.json file will continue to function correctly.

However, if the app transfer is part of a larger business sale where the web domain is also migrating to a new server or web host, you must copy the .well-known/assetlinks.json file to the new web server immediately. Ensure that the target server is configured to serve the JSON payload with the exact same package name and SHA-256 fingerprint. If there is a delay in moving this file to the new domain host, users will experience a broken interface with visible browser chrome.

Handling Upload Keys After the Transfer

While the primary app signing key transfers automatically under Google Play App Signing, the upload key (used to upload your AAB files to the console) can optionally be rotated. For security purposes, it is highly recommended that the target developer generates a new upload key. This prevents the source developer from retaining the ability to sign local binaries that match the target upload credentials.

To establish a new upload key after a transfer, the target developer must generate a new upload keystore locally, export the certificate as a PEM file, and submit an upload key reset request through the Google Play Console under the App Signing setup page. Google will update the registered upload certificate within 1 to 2 business days, allowing the new owner to push updates using their own secure local keys.

Testing the Transferred Application

Once the transfer status is marked as complete in both consoles, run a complete end-to-end verification. Download the application from the Google Play Store under the new developer account. Launch the application on multiple devices to ensure that the Digital Asset Links handshake is successful and that the address bar remains hidden. Additionally, monitor the Google Play Console for any pre-launch report warnings or policy issues that might arise under the new account profile.