Bugs Found in Le Chat by Mistral AI for Android
Le Chat by Mistral AI is a great productivity app with multiple AI-powered features that make your professional and personal life easier. These include AI-assisted search, document OCR processing, deep research with complex reasoning, and data organization.
The app provides a sleek, conversational interface designed for high-performance AI interactions. However, our recent testing on the Android mobile build revealed several critical synchronization and playback defects.
See the results of the QAwerk team’s bug crawl of Le Chat below to understand where the issues are and how they could be rectified by implementing QA best practices.
Sending each message initiates new chat session in history
Severity:
Critical
Precondition:
- Log in to the account.
- Use private mode.
Steps to Reproduce:
- Open a new non-private chat.
- Enter a message in the ‘Ask Le Chat’ input field (e.g., ‘What is my name?’).
- Tap the ‘Send’ button.
- Wait for the AI’s response.
- Enter a follow-up message in the same chat window (e.g., ‘No, my name is QaTester’).
- Tap the ‘Send’ button.
- Open the side menu (history/projects) by clicking the icon in the top left corner.
Environment:
Xiaomi Mi 10
Android 13 TKQ1.221114.001
Xiaomi HyperOS 1.0.1.0
Actual Result:
Each message sent creates a separate chat in the history sidebar. Two separate ‘User’s Identity’ chats are visible, instead of one continuous thread.
Expected Result:
Successive messages within the same conversation should be saved under a single chat entry in the history.
‘Playback Failed’ error while using text-to-speech feature
Severity:
Major
Precondition:
- Log in to the account.
- Have an existing chat with an AI response.
Steps to Reproduce:
- Open a new non-private chat.
- Enter a message in the ‘Ask Le Chat’ input field (e.g., ‘What is my name?’).
- Tap the ‘Send’ button.
- Stop creating a response.
- Tap the ‘Voiceover’ button.
- Restart the response creation.
- Wait for the AI’s response.
- Tap the ‘Voiceover’ button.
Environment:
Xiaomi Mi 10
Android 13 TKQ1.221114.001
Xiaomi HyperOS 1.0.1.0
Actual Result:
A toast notification appears with the message ‘Playback Failed’ and no audio is generated or played.
Expected Result:
The application should trigger the text-to-speech engine and read the message content aloud.
Chat history fails to display image preview after upload
Severity:
Major
Precondition:
Log in to the account.
Steps to Reproduce:
- Tap the ‘+’ button and upload an image from the gallery.
- Type a prompt related to the image (e.g., ‘Describe this meme’) and tap the ‘Send’ button.
- Once the message is sent, observe the chat history bubble where the image should appear.
Environment:
Xiaomi Mi 10
Android 13 TKQ1.221114.001
Xiaomi HyperOS 1.0.1.0
Actual Result:
The image fails to appear in the chat history. In its place, a blank/white rectangular container is displayed. However, the ‘…’ (more options) menu for the image is still accessible.
Expected Result:
The uploaded image should be displayed prominently as a preview within the chat thread, directly above the corresponding text prompt.
Audio playback stops after roughly 1.5 minutes despite longer text content
Severity:
Major
Precondition:
- Log in to the account.
- Have a chat containing a long-form AI response.
Steps to Reproduce:
- Launch the app.
- Navigate to a long-form response (e.g., deep research results).
- Tap the ‘Play’ (speaker icon) to initiate text-to-speech conversion.
- Note the playback duration when it stops automatically.
Environment:
Xiaomi Mi 10
Android 13 TKQ1.221114.001
Xiaomi HyperOS 1.0.1.0
Actual Result:
The audio playback ceases unexpectedly after roughly 1.5 minutes, leaving the remainder of the text unread despite it being completely displayed in the chat.
Expected Result:
The text-to-speech system should flawlessly convert and play the entire text response, regardless of its duration.
‘Playback’ button is missing for first AI response in new chat
Severity:
Major
Precondition:
- Log in to the account.
- Initiate the first chat session.
Steps to Reproduce:
- Enter the first prompt in a fresh chat (e.g., ‘Write a short story (under 200 words) about a robot that discovers it can feel cold. The tone should be melancholic but hopeful’).
- Send the message and wait for the AI to complete its response.
- Check the bottom of the AI message bubble for the ‘Play’ (speaker icon).
Environment:
Xiaomi Mi 10
Android 13 TKQ1.221114.001
Xiaomi HyperOS 1.0.1.0
Actual Result:
The ‘Playback’ button (speaker icon) does not appear for the very first message in the chat history. The button only becomes available for subsequent messages in the same thread.
Expected Result:
The ‘Playback’ button should be visible and functional for all AI responses, including the first one.
Multiple clicks (5+) required to register ‘Dislike’ button action
Severity:
Minor
Precondition:
- Log in to the account.
- Have an AI response visible in the chat.
Steps to Reproduce:
- Launch the app.
- Navigate to any chat with an AI response.
- Locate the ‘Dislike’ (thumbs down) icon at the bottom of the message bubble.
- Tap the button once.
- If no visual feedback or registration occurs, continue tapping until the state changes.
Environment:
Xiaomi Mi 10
Android 13 TKQ1.221114.001
Xiaomi HyperOS 1.0.1.0
Actual Result:
Despite the initial tap, the ‘Dislike’ button does not respond. Repeated clicking (often more than five times) is necessary for the application to register the interaction.
Expected Result:
The ‘Dislike’ button should respond to a single tap, providing immediate haptic or visual feedback to indicate that the rating was recorded successfully.
App automatically resends last message and reloads ‘Limit reached’ notice when navigating back to chat
Severity:
Trivial
Precondition:
- Log in to the account.
- Reach the usage limit for the current model/period to trigger the ‘Limit reached’ message.
Steps to Reproduce:
- Initiate a chat session and send a message that triggers the ‘Limit reached’ notification. This action should not generate an AI response, only the limit warning.
- Navigate away from the current chat (e.g., go to the ‘History’ section and open a different, older chat where the last message was a successful generation).
- Return to the chat session where the limit was previously reached.
- Observe the chat input and the message history.
Environment:
Xiaomi Mi 10
Android 13 TKQ1.221114.001
Xiaomi HyperOS 1.0.1.0
Actual Result:
The application automatically re-triggers the last sent message without any user input and reloads the ‘Limit reached’ page/message.
Expected Result:
Navigating back to a chat should only display the existing history. The app should not automatically resend requests or refresh the limit warning until the user manually interacts with the input field.
Lack of visual distinction for ‘Learn More’ link from non-clickable disclaimer text
Severity:
Trivial
Precondition:
Log in to the account.
Steps to Reproduce:
- Locate the footer text below the input field: ‘Check Le Chat for mistakes. Learn more.’
- Observe the visual styling (color, weight, underlining) of the entire sentence.
- Attempt to tap the ‘Check Le Chat for mistakes.’ section.
- Attempt to tap the ‘Learn more.’ section.
Environment:
Xiaomi Mi 10
Android 13 TKQ1.221114.001
Xiaomi HyperOS 1.0.1.0
Actual Result:
Only the ‘Learn More’ portion of the text is an operational, clickable link. There is no visual distinction (such as a different color or an underline) between the static text and the hyperlink.
Expected Result:
Interactive links should visually stand out from the static text (e.g., through the use of a distinct brand color or an underline) to signify their clickable nature.
During testing, I identified major regressions in session management, where every message initiates a redundant new chat, as well as functional failures in the text-to-speech engine. To ensure a production-ready release, we recommend executing a comprehensive suite of functional and non-functional tests while leveraging QAwerk’s proven approach of combining rigorous regression cycles with compatibility testing across diverse hardware environments.
