Skip to main content

Kōkua: Chat Mode Not Responding (iOS and Android)

Known issue: Kōkua's chat mode may not respond to messages on iOS and Android.

Written by Sylvie Howell
Updated yesterday

⚠️ This is a Known Issue We're Actively Working On

Our engineering team has confirmed a bug where Kōkua's chat mode stops responding to messages on both iOS and Android. You may type a message and see it sent, but Kōkua does not reply — the chat appears to hang or freeze.

We understand how disruptive this is and we're actively working on a resolution. This article will be updated as soon as a fix is available.

What's Happening

In chat mode, you may experience:

  • Messages sent but no response from Kōkua

  • The typing indicator appearing indefinitely without a reply

  • Kōkua responding to one or two messages then going silent

  • The chat interface freezing or becoming unresponsive

  • Messages appearing to send but no confirmation or reply arriving

Workaround

These steps may help in the meantime:

  • Switch to voice mode — If chat is unresponsive, try switching to voice/microphone mode to interact with Kōkua.

  • Close and reopen the Kōkua bubble — Dismiss Kōkua entirely and re-engage it. This may reset the chat session.

  • Restart the TRIPP app — Close the app fully (swipe away from the app switcher) and relaunch. This often temporarily restores chat functionality.

  • Wait and retry — Occasionally the issue self-resolves after 30–60 seconds. If Kōkua shows a typing indicator, give it a moment before closing.

Will Standard Troubleshooting Help?

Because this is a confirmed platform-level bug, clearing cache, reinstalling the app, or updating your OS are unlikely to permanently resolve this issue. A restart of the app may provide temporary relief, but the bug can recur within the same session.

Stay Updated

We'll update this article when the fix is deployed. If you'd like a direct update when chat mode is fully restored, contact us at support@tripp.com with "Kōkua chat mode bug" — we'll notify you personally when it's resolved.

Did this answer your question?