Open ldm0330 opened 1 year ago
@ldm0330 I am not able to reproduce this. Is still happening on the latest version? Does it happen always?
@ldm0330 I am not able to reproduce this. Is still happening on the latest version? Does it happen always?
Thank you for your reply. We also found that this problem occurs only with the Samsung model SM-G7810. Now we are using the latest server and client versions. I still haven't found the cause of this problem,This problem will inevitably appear, but it will only appear when the other party has never opened a private message to chat with the other party. The mobile phone information is in the screenshot below
@ldm0330 There has been recent changes on how we handle some of this. Do you mind testing if this is still happening to you in the latest beta?
The current version from Google Play (App 2.9.0, see screenshot below) still does not work reliably when sending the first private message to a user.
For new private chats, the first message pops up for an instant, but then disappears. Apart from that initial blink, that first message will not show anymore, while the second message appears instantly (only the second message! - see attached screen recording). After completely closing and reopening the app, both messages appear as expected.
The screen recording below is from a Pixel 7 with Android 14, but we have observed this behavior on different Pixel phones (Pixel 4a with Android 13, 2x Pixel 6a with Android 14, Pixel 7a with Android 14). On two other, non-Google phones with older Android versions, the initial message is visible instantly.
When sending only a single message, the message still does not show up after closing and reopening the app. https://github.com/mattermost/mattermost-mobile/assets/20656284/37f28620-dcab-4737-afe7-a79c0a6a0f6a
I am also affected by this bug.
Phone: Pixel 6a, Android 14
App Version: App Version: 2.10.1 (Build 6000496) Server Version: 9.2.2 (Build 6801073174 Database: postgres Database Schema Version: 113
Greetings
@larkox Do you need any more information on this issue? We are sadly running into the described problem repeatedly.
Please check the video presentation for details
https://user-images.githubusercontent.com/34537273/220097065-9e8250a9-9d68-4a65-bfb1-ce789382ee6a.mp4