Firebase App Distribution关联Google Play时遇到权限缺失问题

Let me walk you through the most common fixes for this permission issue, since you've already covered all the basic prerequisites:

• Verify the Google Play Android Developer API is enabled
  Firebase relies on this API to communicate with Google Play, even if you're an account Owner. Head to your Google Cloud Console (tied to your Firebase project), search for "Google Play Android Developer API" and confirm it’s set to "Enabled". If it was disabled, turn it on and wait 5-10 minutes for the change to propagate before retrying the link.

• Re-authorize the Firebase-Google Play connection
  Sometimes the initial authorization fails to grant all necessary permissions properly. Go to your Firebase project's Settings > Integrations, find the Google Play card, click "Manage" then "Disconnect". Wait a minute, then re-initiate the linking process. When the Google account permission prompt pops up, make sure to check all requested permissions (don’t skip any) before confirming.

• Wait for Play Store data sync
  Even if your app is live in Production, it can take 2-3 hours for Play Store data to fully sync with Firebase’s systems. If you just published the app recently, hold off on linking until the Play Console shows no pending statuses for your release, then try again.

• Confirm consistent account ownership
  Double-check that you’re logged into the exact same Google account in both Firebase Console and Google Play Console. It’s easy to accidentally switch between personal and work accounts without noticing—log out of both consoles, clear your browser cache, then log back in with the correct Owner account before attempting the link.

• Check Firebase service account permissions
  In your Firebase project's Settings > Service Accounts, locate the "Firebase App Distribution Service Agent" account. Jump to the Google Cloud Console’s IAM section, find this service account, and ensure it has these roles assigned:

  • Firebase App Distribution Admin
  • Google Play Developer Service Account (or at minimum, View App Information and Manage Releases permissions for your target app)

If none of these steps resolve the issue, try creating a test app in both Firebase and Play Console with a unique package name, publish it to a closed track, and attempt linking—this can help isolate if the problem is specific to your existing app or a broader account configuration quirk.

内容的提问来源于stack exchange，提问作者jwBurnside