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

Reactions are incorrectly positioned on chat bubbles #2030

Open
andreaslydemann opened this issue Mar 30, 2023 · 1 comment
Open

Reactions are incorrectly positioned on chat bubbles #2030

andreaslydemann opened this issue Mar 30, 2023 · 1 comment

Comments

@andreaslydemann
Copy link
Contributor

andreaslydemann commented Mar 30, 2023

Describe the bug
Whenever I add a reaction to a chat bubble that isn't my own message, the reaction is positioned too far to the right. It should be positioned on the edge of the chat bubble, just like when a reaction is added to any of my messages.

Dev environment info (please complete/provide the following information):

  • stream-chat-expo: 5.7.0
  • expo: 46.0.20
  • react-native": 0.70.5
  • iOS device (iOS 16.2)

To Reproduce
Steps to reproduce the behavior:

Add a reaction to a message from someone else than yourself. Notice how it's not positioned correctly. It's positioned far to the right of the chat bubble. I even tried in the iMessage clone from react-native-samples and I see the same problem there. I attached a screenshot from that project.

Expected behavior
I expect the reaction to be positioned the same place as when a reaction is added to my own messages (right on the edge of the chat bubble without any spacing between the reaction and the chat bubble).

Simulator Screen Shot - iPhone 14 - 2023-03-28 at 19 25 24

@andreaslydemann andreaslydemann changed the title Reactions added to chat bubbles are incorrectly positioned Reactions are incorrectly positioned on chat bubbles Mar 30, 2023
@khushal87
Copy link
Member

Hello @andreaslydemann, thanks for reporting this bug. This happens in the iMessagClone because we set MessageAvatar to null. I think in your use case, too, you might be setting the MessageAvatar to null, which might be the reason this is happening. Although I agree that this shouldn't happen if we set the message avatar to null since a customer can have this kind of implementation. We will try to fix this is the future.

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

No branches or pull requests

2 participants