Google Play: Migrating From an OAuth Reply to Reviews Integration

Article author
Anastasia
  • Updated

Overview

If you've set up a Reply to Reviews (aka "Reviews & Replies") integration with Google Play for any of your apps prior to Spring 2022, you most likely have the legacy one added through the outdated OAuth method. 

The OAuth service is an authentication method: it's what we use in place of an email and password to connect your AppFollow account to your Google Play Console. While OAuth is a popular authentication method, it's just one of the numerous authorization methods that exist.

On October 3rd, 2022, Google Play will be discontinuing the OAuth authentication method in favor of alternative authentication methods. This means that the legacy OAuth integrations that were set up in AppFollow will cease to work.

To ensure that your Reply to Reviews integrations remain active, we have introduced the new setup methods: Invitation Method (Simple) and Service Account Method (Advanced).

This article will walk you through the steps you need to take before October 3rd to ensure that your integrations remain active.

This guide goes over the steps you need to take to migrate your existing integrations to the new methods. If you need to set up an additional integration during this process, please add the new integration after you migrate your existing ones.

Video Tutorial

I Don't Have Any Integrations Yet

If you don't have an existing Reply to Reviews integration with Google Play yet, you can just set up a new one. To do that, follow our step-by-step setup guide:

I Have Existing OAuth Integrations, and I Have Only One Google Play Developer Account

To make sure the migration process goes smoothly, our system will automatically scan through all of your existing integrations and workspaces as soon as you set up a new integration.

To launch the process:

  1. Open the Integrations page from the left-hand navigation menu.
  2. In the app picker at the top of the view, select the Google Play app you need to integrate.
  3. Choose to set up a Google Play integration.
  4. Follow the steps in our guide on setting up integration via Invitation Method (Simple) or Service Account Method (Advanced).
  5. All of your existing Google Play integrations will be automatically migrated to the new type of integration as soon as you set up a new integration.

I Have Existing OAuth Integrations, and I Have Multiple Google Play Developer Accounts

If you have apps from multiple developer accounts in Google Play, the process is similar to setting up new integrations for apps from a single account. The difference is that you will set up one integration for one app from each of your Google Play developer accounts. For example, if you have 5 apps from one developer account, and 5 apps from another, you will set up 2 integrations: one for any app from the first account, and one for any app from the second account.

To launch the process:

  1. Open the Integrations List page from the left-hand navigation menu in AppFollow.
  2. Select one of the Google Play apps from the app picker at the top of the view.
  3. Choose to set up a Google Play integration.
  4. Follow the steps in our guide on setting up integration via Invitation Method (Simple) or Service Account Method (Advanced).
  5. All of your existing Google Play integrations will be automatically migrated to the new type of integration as soon as you set up a new integration.
  6. Repeat these steps for an app from other developer accounts.

I Have Both a Service Account and OAuth Integration Already Active in My Account

Google Play Service account and Google Play OAuth integrations can not work together. During 30 minutes after the Google Play Service account integration is configured, we will automatically remove the Google Play OAuth integration. 

Contact the Support team if you need help with the migration from OAuth to one of the new methods. 

 

Was this article helpful?

0 out of 0 found this helpful