Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: Text Input Field Not Visible by Default in New Direct Messages #6211

Open
jjinendra3 opened this issue Mar 7, 2025 · 5 comments
Open
Labels

Comments

@jjinendra3
Copy link
Contributor

Describe the Bug

When starting a direct message with a user for the first time, the chat screen opens, but the text input field is not visible by default. However, clicking on the blank space where the input field should be does bring it up, and it functions normally.

Steps to Reproduce

  1. Go to any thread, chat, or community.
  2. Click on the icon of a user you have never contacted before.
  3. Click on the "Message" button on the user's profile.
  4. Observe that the text input field is missing initially.
  5. Click on the blank space where the input should be, and it appears.
WhatsApp.Video.2025-03-07.at.14.10.13_86b0ee9b.mp4

Expected Behavior

The Text Input should be shown normally upon going to an previosuly unvisted direct message.

Like this

Actual Behavior

No response

Rocket.Chat Server Version

7.4.0

Rocket.Chat App Version

4.59

Device Name

S23

OS Version

14

Additional Context

This issue only occurs when messaging a user for the first time. Once a conversation has been initiated (even if no messages are exchanged), the text input field appears as expected in subsequent interactions.

@jjinendra3
Copy link
Contributor Author

Hey @diegolmello , could you please share your thoughts on this? Thanks.

@Rohit3523
Copy link
Contributor

Unable to reproduce this issue, getting toast message

Screenrecording_20250307_150401.mp4

@jjinendra3
Copy link
Contributor Author

Unable to reproduce this issue, getting toast message

Screenrecording_20250307_150401.mp4

Your direct message access is restricted it seems.

@diegolmello
Copy link
Member

It's a valid bug.
I've seen it happening, but couldn't find a way to reproduce it.
Can you fix it?

@jjinendra3
Copy link
Contributor Author

Sure! I will take this up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants