Troubleshooting & Common Errors

If you experience issues with the KiviCare Google Meet integration, this troubleshooting guide will help you identify and resolve the most common problems quickly.

Issue: Google Meet Link Not Showing in Appointment

The appointment is created successfully, but the “Join Google Meet” button does not appear.

Possible Solutions

• Verify Service Configuration
  Ensure the selected service has Telemedicine enabled and Google Meet chosen as the consultation provider.
• Check Doctor Connection Status
  Open the doctor’s profile or settings and confirm that the Google Meet status shows Connected.
• Review Log Files
  Check the KiviCare log files for any WP_Error responses from the Google Calendar API.

Issue: “Invalid Access Token” or 401 Unauthorized Error

This error usually occurs when the OAuth authentication token has expired or the authorization process was interrupted.

Possible Solutions

• Reconnect the Google Account
  Ask the doctor to disconnect and reconnect their Google account from KiviCare.
• Confirm SSL Configuration
  Google requires a valid HTTPS (SSL) connection for all OAuth requests.
• Validate API Scopes
  Make sure your Google Cloud project includes the required scope:
  https://www.googleapis.com/auth/calendar

Issue: “Redirect URI Mismatch” Error

Google displays a redirect URI mismatch error during authorization.

Solution

• Confirm that the Authorized Redirect URI in the Google Cloud Console exactly matches the URI shown in KiviCare Google Meet settings, typically:
  YOUR_SITE_URL/wp-json/kivicare/v1/settings/googlemeet/callback

Quick Troubleshooting Checklist

1. Reconnect Google Account
   Disconnecting and reconnecting is the fastest way to resolve token-related issues.
2. Confirm API Availability
   Ensure the Google Calendar API is enabled in your Google Cloud Console.
3. Check API Quotas
   Verify that your project has not exceeded Google’s daily API usage limits.

Escalating the Issue to Support

If the problem persists after following the steps above:

1. Enable WP_DEBUG in your WordPress configuration.
2. Reproduce the issue by creating a new appointment.
3. Copy the error details from wp-content/debug.log.
4. Submit a support ticket to IQONIC Support at:
   https://apps.iqonic.design/support/