You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made sure that there are no existing issues - open or closed - which I could contribute my information to.
I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
This issue contains only one bug, that only occurs in Squawker
Affected version
v3.1.2+300003146
Steps to reproduce the bug
Go to the "Feed" tab.
See retweets from people you're subscribed to.
Notice the wrong username.
Check the user's profile to see the right one.
Expected behavior
Retweets in the "Feed" should display the Original username and profile picture first, with a "[user] retweeted [time] ago" like they did before and they currently do in each profile.
Actual behavior
Retweets in the "Feed" show the username and profile picture of the user who did the retweet, instead of the user who did the first post.
They also display:
-The text RT@[OGusername]
A non-clickable t.co link pointing to the original tweet.
Screenshots/Screen recordings
No response
Logs
No response
Affected Android/Custom ROM version
No response
Affected device model
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Checklist
Affected version
v3.1.2+300003146
Steps to reproduce the bug
Expected behavior
Retweets in the "Feed" should display the Original username and profile picture first, with a "[user] retweeted [time] ago" like they did before and they currently do in each profile.
Actual behavior
Retweets in the "Feed" show the username and profile picture of the user who did the retweet, instead of the user who did the first post.
They also display:
-The text RT@[OGusername]
Screenshots/Screen recordings
No response
Logs
No response
Affected Android/Custom ROM version
No response
Affected device model
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: