Bugs Found in Bluedot AI Note Taker for Android
Bluedot is an AI-powered app for recording, transcribing, and even summarizing meetings. It helps you track online and offline meetings, as well as phone calls. It effectively integrates with Google Meet, Zoom, and Microsoft Teams to record calls there.
The QAwerk team tested the Bluedot app for Android during our regular bug crawl. We found that while the core functionality was solid, the app had bugs when handling state changes. Take a look at our findings and the QA engineer’s recommendations below.
Malformed request error is displayed when reselecting transcript language while transcription is in progress
Severity:
Major
Precondition:
- The app is installed.
- A recording has been completed.
Steps to Reproduce:
- Open the created recording.
- Switch to the ‘Transcript’ tab.
- Select the language.
- Change the language.
Environment:
Samsung Galaxy A35, Android version 14, One UI version 6.1
Actual Result:
A technical HTTP 400 error dialog is displayed stating that the recording is already being transcribed.
Expected Result:
The app should prevent another transcription request while transcription is already in progress. The transcript language selection should be disabled or unavailable until the current transcription is completed, or the action should be handled gracefully without exposing a technical backend error.
Transcript does not recognize second speaker
Severity:
Major
Precondition:
The app is installed.
Steps to Reproduce:
- Start a new recording.
- Have Speaker A speak several phrases.
- Have Speaker B say a phrase.
- Finish the recording.
- Wait until transcription is completed.
- Open the transcript.
Environment:
Samsung Galaxy A35, Android version 14, One UI version 6.1
Actual Result:
Only Speaker A is identified in the transcript. Speaker B’s phrase is not recognized as belonging to a separate speaker.
Expected Result:
The transcript should recognize Speaker B as a separate speaker and attribute their speech accordingly.
Recording continues without audio capture during active phone call
Severity:
Major
Precondition:
- The app is installed.
- A recording has been started.
Steps to Reproduce:
- Record a phrase.
- Receive and answer an incoming phone call.
- Keep the call active for about 25 seconds.
- End the call.
- Speak another phrase.
- Finish and play the recording.
Environment:
Samsung Galaxy A35, Android version 14, One UI version 6.1
Actual Result:
The recording continues, and the timer keeps counting while the phone call is active. However, no audio is captured during the call, resulting in a silent segment in the final recording.
Expected Result:
The app should properly handle audio capture interruption during an active phone call and inform the user when it cannot record audio.
Keyboard overlaps ‘Invite’ email field on ‘Share via link’ screen
Severity:
Major
Precondition:
- The app is installed.
- A recording details page is open.
Steps to Reproduce:
- Click the ‘Share’ button.
- Place the cursor in the input field next to the ‘Invite’ button.
Environment:
Samsung Galaxy A35, Android version 14, One UI version 6.1
Actual Result:
The keyboard overlaps the ‘Invite’ email input field, preventing the user from clearly seeing the entered email address.
Expected Result:
The ‘Invite’ email field should remain visible above the keyboard when it receives focus.
Connection error remains displayed until user switches tabs
Severity:
Major
Precondition:
The app is installed.
Steps to Reproduce:
- Start the recording.
- Enable Airplane Mode.
- Finish the recording.
- Observe the connection error.
- Disable Airplane Mode and restore the internet connection.
- Wait for the recording upload to retry.
- Observe the connection error without leaving the current tab.
- Switch to another tab and return.
Environment:
Samsung Galaxy A35, Android version 14, One UI version 6.1
Actual Result:
The connection error remains displayed after the internet connection is restored and the upload is retried. The error disappears/updates only after the user switches to another tab and returns.
Expected Result:
The connection error should clear automatically, and the upload status should update on the current screen once the connection is restored and the upload is successfully retried.
Uploaded profile photo is not displayed until ‘Settings’ tab is reopened
Severity:
Minor
Precondition:
The user is on the ‘Settings’ tab.
Steps to Reproduce:
- Upload a photo.
- Verify that the ‘Photo uploaded successfully’ confirmation message is displayed.
- Check the photo.
- Reopen the ‘Settings’ tab.
Environment:
Samsung Galaxy A35, Android version 14, One UI version 6.1
Actual Result:
The success message is displayed, but the newly uploaded profile photo is not shown. The photo appears only after reopening the ‘Settings’ tab.
Expected Result:
The newly uploaded profile photo should display immediately after a successful upload, without requiring the user to leave and reopen the ‘Settings’ tab.
Recording duration is incorrectly rounded to minutes in shared recording email
Severity:
Minor
Precondition:
The app is installed.
Steps to Reproduce:
- Create a recording shorter than 1 minute (e.g., 16 seconds).
- Finish the recording.
- Verify the duration displayed in the app.
- Share the recording via email.
- Open the received email.
- Compare the displayed recording duration.
Environment:
Samsung Galaxy A35, Android version 14, One UI version 6.1
Actual Result:
The app correctly displays the recording duration as 16 seconds, while the shared recording email displays it as 1 minute.
Expected Result:
The recording duration in the shared email should accurately reflect the recording duration and match the duration displayed in the app.
When testing the app, I determined that the main areas for improvement include handling edge cases and maintaining synchronization between the User Interface and the application's actual state. Further efforts should focus on network recovery, system interruptions (for example, phone calls), transcription processing states, speaker recognition, and user-oriented error handling.
