This section describes common issues that you can encounter while building and testing Chat apps.
A card message, dialog, or link preview doesn't render or work as expected
For help troubleshooting card errors, see Troubleshoot and fix cards.
App is not responding
If you message the Chat app and it responds "App is not responding," verify the Chat app's configuration:
In the Google Cloud console, click Menu > More products > Google Workspace > Product Library > Google Chat API > Manage > Configuration.
Under App status, make sure that you selected Live - available to users.
Under Interactive features, make sure that settings are appropriate for your app's functionality. If your Chat app interacts with users, make sure you turn on Enable interactive features:
- If your app responds to messages, make sure you select Receive 1:1 messages.
- Under Connection settings, make sure the App URL, Apps Script project Deployment ID, Cloud Pub/Sub Topic Name, or Dialogflow agent is set correctly and that it is deployed.
- Under Visibility, make sure the appropriate users have access to the app with email address or a group in the Google Workspace domain. If the app is deployed with Google Workspace Marketplace SDK, visibility settings aren't necessary because Google Workspace Marketplace settings take precedence.
If the app is published with Google Workspace Marketplace SDK, review Google Workspace Marketplace settings.
Click Save.
Try messaging the app again.
Google Chat API is only available to Google Workspace users
When configuring the Chat app, you might receive the
error Google Chat API is only available to Google Workspace users. This message
means that the Google Account that you've used to configure the
Chat API isn't part of a Google Workspace organization. To build a
Chat app or use the Chat API, you must use a
Google Workspace
account.
Note that Google Chat users can use Chat apps without a Google Workspace account. To learn more about how users discover and install Chat apps, see Publish Google Chat apps.
Users can be excluded from spaces
If a Google Workspace administrator disallows users to turn Chat history on or off, then there might be times when users can't join or stay in a space due to a conflict between a user-level setting that forces chat history on or off and a space that inherits the organization-level forced setting.
For example, if a user has a Chat history setting forced "on" and a space has a Chat history setting forced "off", then that user might not be able to join the space. Additionally, that user might be removed from the space if they joined prior to the conflict and then they post a message in the space after the conflict.
In this scenario, and other scenarios where there are conflicts between history settings, Chat API might not be able to create a membership, or creating a message with user authentication might remove the authenticated user with a conflicting Chat history setting from the space.
To learn more, see Users can be excluded from spaces in the Google Workspace Admin Help center.
Troubleshoot the Advanced Chat service in Google Apps Script
See the Apps Script page about the Advanced Chat Service.
Users are unable to add a Chat app to a space
If users encounter the error message
This organization's administrator must allow users to install this Chat app
when trying to add a Chat app to a space, this error
might be caused by one of the following reasons:
- The organization has disabled Chat apps.
- The organization hasn't added this specific Chat app to the organization's allowlist.
If a user encounters this error message when trying to interact with a Chat app, it might be caused by the organization granting access to a sub-organizational unit, without enabling it for the parent organizational unit.
For information about how to resolve this issue, see Allow users to install Chat apps.
Troubleshoot Cloud Function errors
If the Chat app is implemented with Cloud Functions and it isn't working, the following sections help troubleshoot and fix the issue.
Check Cloud Function logs
As a first step, check the Cloud Functions logs for errors.
In the Google Cloud console, go to the Cloud Functions page:
To open the logs, find your Chat app's Cloud Function, then click Show actions > View logs.
The Logs Explorer opens and runs a query showing Cloud Function logs, including errors.
If the default information logged is not enough to debug your app, you can add additional logging from your Cloud Function code. See View and write Cloud Function logs.
Check Cloud Function errors
Apart from the logs, Cloud Function might also report errors encountered while running.
In the Google Cloud console, go to the Cloud Functions page:
Click your Chat app's Cloud Function.
On the Function details page, errors are listed under Errors.
To further troubleshoot an error, click it.
Fix common Cloud Function errors
The following errors are sometimes encountered when building a Chat app with Cloud Functions.
Function ChatApp in region REGION_NAME in project PROJECT_NAME already exists
When deploying a Cloud Function, you might receive the error Function
ChatApp in region REGION_NAME in project PROJECT_NAME already
exists. This message means that another Cloud Function has the same name as the
one you're deploying. Change the name, and
deploy the function again. Verify that the Chat app uses the Trigger URL for
your Cloud Function, not the Trigger URL of the preexisting Cloud Function.
One or more users named in the policy do not belong to a permitted customer
When deploying a Cloud Function, you might receive the error The operation
cannot be completed on the function: "One or more users named in the policy do
not belong to a permitted customer." If you get this error and then message the
Chat app, you get an error saying that the app isn't responding because Google
Chat can't reach the server hosting the Cloud Function. This message means that
a user named "allUsers" doesn't have permission to call the Cloud Function.
Giving "allUsers" the "Cloud Functions Invoker" role means that the Cloud
Function that powers the app is publicly available and accessible without
authentication. To learn how to assign a role, see
Grant a single role.
This error might mean that the Google Cloud project is domain restricted. For more information about domain restriction constraints, refer to Restricting identities by domain.
To resolve this issue, verify that your Cloud Function allows unauthenticated invocations. To learn how to allow unauthenticated invocations for an existing Cloud Function, refer to Allowing public (unauthenticated) access.