[Feature Request / Bug] Android & iOS SDK: Draft text is lost during back navigation in IntercomSpace.Home | Community
Skip to main content
Submitted

[Feature Request / Bug] Android & iOS SDK: Draft text is lost during back navigation in IntercomSpace.Home

Related products:Messenger
  • August 24, 2026
  • 0 replies
  • 1 view
M
  • Mai
  • New Participant

Description: When using Intercom.client().present(IntercomSpace.Home) on both Android and iOS Mobile SDKs, users experience total loss of input text if they navigate away from an active thread.

Steps to Reproduce:

  1. Launch Intercom using IntercomSpace.Home.

  2. Tap on an existing chat or start a new message under "Contact Support".

  3. Type a message into the input field, but do not tap send.

  4. Tap the top-left back arrow (←) or hardware back button to return to the Home space.

  5. Re-open the same chat or message composer.

Expected Behavior: Unsent draft text should be retained in the input composer when the user returns to the thread view.

Actual Behavior: The input field is completely cleared, forcing the user to re-type their entire message. This causes high friction, particularly when users navigate away to copy details from other screens in our app.

Environment:

  • Platforms: Android & iOS SDKs

  • Method Used: Intercom.client().present(IntercomSpace.Home)

Terms & ConditionsAccessibility statement