Common Linked Account Problems

It is possible your Linked Account can cease to function, causing data to stop making its way into Appbot.

Here are some common causes and how to fix them. They are specific to the type of Linked Account.

Google Play

Problem: “forbidden: Forbidden”

This is by far the most common error we see and is a bit of a catch-all.
Some causes:

  • The account has been disabled or removed via the Google Play Developer Console under¬†Settings > API Access > Service Accounts
  • Account permissions do not allow access to the app. Check the app listed on the Appbot problems screen is in the list of permitted apps in the Google Play Developer Console under Settings > API Access > Service Accounts > View Permissions.

To fix this please revisit our support article and check all settings and permissions are as indicated.

Problem: “Service Account key issue: invalid_grant Invalid JWT Signature.”

This error indicates that the credentials for your Linked Account are no longer valid. You will need to re-link it to Appbot.

Microsoft

Problem: 401 – “A valid account could not be found”

This error indicates that the credentials for your Linked Account are no longer valid. Please re-link it to Appbot.