[M2.7 Bug]

Which inference path did you use?

MiniMax Agent

Inference parameters

No response

Prompt / input

Title: [Mobile/Tablet] Chat state lost on screen rotation — no persistence

Environment:
- Platform: Android tablet (likely Android 14/15 based on UI)
- App: MiniMax-M3 mobile/tablet build
- Model selected: MiniMax-M3

Severity: High — data loss

Description:
On Android tablets, rotating the screen (portrait ↔ landscape) while a chat
is active wipes the entire conversation. The chat reverts to the empty
"How can I help you?" start screen. There is no warning, no auto-save, no
recovery.

Reproduction:
1. Open MiniMax-M3 on Android tablet
2. Start a chat, send at least one message, get a response
3. Rotate the device from portrait to landscape (or back)
4. Observe: chat is gone, app returns to fresh start state

What works (control test):
- Switching to another app and returning to MiniMax keeps the chat
- Killing and reopening the app keeps the chat (mostly — see below)

Related issue:
- Chat history sidebar shows "No chat history yet" — it appears conversations
  are not being saved server-side or client-side either. Switching the
  device, signing in on another device, etc. would not recover lost work.

Expected behavior:
- Screen rotation should preserve chat state (configChanges in manifest
  should include "orientation|screenSize|keyboardHidden", OR state should
  be persisted to ViewModelStore/SavedStateHandle, OR persisted to
  localStorage/IndexedDB in the webview).
- Conversations should auto-save to a recoverable history.

Actual behavior:
- Full chat loss, no recovery, no warning.

Screenshots: attached (before/after rotation)

Expected behavior

Title: [Mobile/Tablet] Chat state lost on screen rotation — no persistence

Environment:

• Platform: Android tablet (likely Android 14/15 based on UI)
• App: MiniMax-M3 mobile/tablet build
• Model selected: MiniMax-M3

Severity: High — data loss

Description:
On Android tablets, rotating the screen (portrait ↔ landscape) while a chat
is active wipes the entire conversation. The chat reverts to the empty
"How can I help you?" start screen. There is no warning, no auto-save, no
recovery.

Reproduction:

1. Open MiniMax-M3 on Android tablet
2. Start a chat, send at least one message, get a response
3. Rotate the device from portrait to landscape (or back)
4. Observe: chat is gone, app returns to fresh start state

What works (control test):

• Switching to another app and returning to MiniMax keeps the chat
• Killing and reopening the app keeps the chat (mostly — see below)

Related issue:

• Chat history sidebar shows "No chat history yet" — it appears conversations
  are not being saved server-side or client-side either. Switching the
  device, signing in on another device, etc. would not recover lost work.

Expected behavior:

• Screen rotation should preserve chat state (configChanges in manifest
  should include "orientation|screenSize|keyboardHidden", OR state should
  be persisted to ViewModelStore/SavedStateHandle, OR persisted to
  localStorage/IndexedDB in the webview).
• Conversations should auto-save to a recoverable history.

Actual behavior:

• Full chat loss, no recovery, no warning.

Screenshots: attached (before/after rotation)

Actual behavior

Title: [Mobile/Tablet] Chat state lost on screen rotation — no persistence

Environment:

• Platform: Android tablet (likely Android 14/15 based on UI)
• App: MiniMax-M3 mobile/tablet build
• Model selected: MiniMax-M3

Severity: High — data loss

Description:
On Android tablets, rotating the screen (portrait ↔ landscape) while a chat
is active wipes the entire conversation. The chat reverts to the empty
"How can I help you?" start screen. There is no warning, no auto-save, no
recovery.

Reproduction:

1. Open MiniMax-M3 on Android tablet
2. Start a chat, send at least one message, get a response
3. Rotate the device from portrait to landscape (or back)
4. Observe: chat is gone, app returns to fresh start state

What works (control test):

• Switching to another app and returning to MiniMax keeps the chat
• Killing and reopening the app keeps the chat (mostly — see below)

Related issue:

• Chat history sidebar shows "No chat history yet" — it appears conversations
  are not being saved server-side or client-side either. Switching the
  device, signing in on another device, etc. would not recover lost work.

Expected behavior:

• Screen rotation should preserve chat state (configChanges in manifest
  should include "orientation|screenSize|keyboardHidden", OR state should
  be persisted to ViewModelStore/SavedStateHandle, OR persisted to
  localStorage/IndexedDB in the webview).
• Conversations should auto-save to a recoverable history.

Actual behavior:

• Full chat loss, no recovery, no warning.

Screenshots: attached (before/after rotation)

Additional context

Title: [Mobile/Tablet] Chat state lost on screen rotation — no persistence

Environment:

• Platform: Android tablet (likely Android 14/15 based on UI)
• App: MiniMax-M3 mobile/tablet build
• Model selected: MiniMax-M3

Severity: High — data loss

Description:
On Android tablets, rotating the screen (portrait ↔ landscape) while a chat
is active wipes the entire conversation. The chat reverts to the empty
"How can I help you?" start screen. There is no warning, no auto-save, no
recovery.

Reproduction:

1. Open MiniMax-M3 on Android tablet
2. Start a chat, send at least one message, get a response
3. Rotate the device from portrait to landscape (or back)
4. Observe: chat is gone, app returns to fresh start state

What works (control test):

• Switching to another app and returning to MiniMax keeps the chat
• Killing and reopening the app keeps the chat (mostly — see below)

Related issue:

• Chat history sidebar shows "No chat history yet" — it appears conversations
  are not being saved server-side or client-side either. Switching the
  device, signing in on another device, etc. would not recover lost work.

Expected behavior:

• Screen rotation should preserve chat state (configChanges in manifest
  should include "orientation|screenSize|keyboardHidden", OR state should
  be persisted to ViewModelStore/SavedStateHandle, OR persisted to
  localStorage/IndexedDB in the webview).
• Conversations should auto-save to a recoverable history.

Actual behavior:

• Full chat loss, no recovery, no warning.

Screenshots: attached (before/after rotation)

No files, tests, or entry points are named. Start by locating the Android configuration and chat state lifecycle, then reproduce rotation on a tablet and trace why the active conversation is discarded. Done means the conversation remains visible after rotation and is recoverable through chat history, with a regression test if the project has one.