I have:
Messages change to last messages seen at bottom or top of screen depending on direction while scrolling through message history. I have a secondary phone (Huawei P8lite) that does not appear to exhibit the same problem.
First noticed this issue with Signal 3.28.4
Actual result: Messages do not correspond to history
Expected result: Messages should be as it were.

Device: Samsung Galaxy J5 2016 (SM-J510GN)
Android version: 6.0.1
Signal version: 3.29.6
https://gist.github.com/tsdmgz/4f06f5369288a2e3cc8153748efde8db
whoa that's bizarre, do you notice it in all threads? even fairly short ones?
I also have the exact same issue. It started with the update prior to introducing video calls. It happens, for me, on all threads. It happens on short ones too as long as there are enough messages to scroll a full page or more.
If you keep scrolling it seems to change the messages around more but never goes back to the correct way until you close the thread and open it back up. But if you scroll again it happens again.
I've been meaning to submit this bug and I'm glad to see someone else did and it's not just me.
@WDKevin Thanks that sounds really annoying. @tsdmgz mentions fast scrolling, is it fast scrolling for you as well, or any scrolling?
@moxie0
just tried and yes, also happens on threads with less than 100 messages.
@WDKevin
relieved to know it's also not just me. is your phone a samsung, by any chance?
@tsdmgz i saw this happening on a friend's samsung some months ago, i think - at least the last message was just gone after scrolling up and down.
@moxie0 Yes, it is fast scrolling. It's very annoying, it makes it impossible to read the history of the conversation.
@tsdmgz Yes, it is a Samsung. It's a Note 4.
@WDKevin huh. following ours and @Trolldemorted, guess our pattern is all samsungs so far.
@tsdmgz @WDKevin This doesn't reproduce on any of the devices I have. If I were to give you a signed APK, would you have time to test it? There are a lot of changes that could be the culprit, so we might have to go through a few iterations.
(alternately under the very rare possibility that you're building and installing from source yourselves, git-bisect would be really useful)
Willing to ~dissect~ bisect and started one from v3.25.0 and 7d1056057. Is there a better starting point or are there any special instructions (aside from backups) or do I just follow BUILDING.md?
Are you sure it was ok on 3.25.0?
I saw the message disappearing several months ago, but it could have been a different issue.
Unfortunately, no. I don't even know which version was good. All I remember was I first noticed this problem by around 3.28 or so.
Also, I seem to be having problems building?
~~~
Could not resolve all dependencies for configuration ':compile'.
Could not find com.android.support:appcompat-v7:25.1.0.
Searched in the following locations:
https://repo1.maven.org/maven2/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.pom
https://repo1.maven.org/maven2/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.jar
https://raw.github.com/whispersystems/maven/master/preferencefragment/releases/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.pom
https://raw.github.com/whispersystems/maven/master/preferencefragment/releases/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.jar
https://raw.github.com/whispersystems/maven/master/smil/releases/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.pom
https://raw.github.com/whispersystems/maven/master/smil/releases/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.jar
https://raw.github.com/whispersystems/maven/master/shortcutbadger/releases/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.pom
https://raw.github.com/whispersystems/maven/master/shortcutbadger/releases/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.jar
https://raw.github.com/whispersystems/maven/master/photoview/releases/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.pom
https://raw.github.com/whispersystems/maven/master/photoview/releases/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.jar
https://dl.bintray.com/amulyakhare/maven/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.pom
https://dl.bintray.com/amulyakhare/maven/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.jar
https://jcenter.bintray.com/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.pom
https://jcenter.bintray.com/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.jar
file:/home/gjie/.m2/repository/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.pom
file:/home/gjie/.m2/repository/com/android/support/appcompat-v7/25.1.0/appcompat-v7-25.1.0.jar
Required by:
:Signal-Android:unspecified
~~~
and several other files
Edit: found it. Other build deps wasn't installed for some reason.
just finished bisecting and it's pointing to 7286fd9b06ec582bfd4ed83dd81a461564806250 as the first bad commit. i've been instaling Signal-Android-debug.apk
debug log: https://gist.github.com/tsdmgz/735a513508df11cfa5ac6ce6bea5e662
I can confirm, I have the same issue on a Fairphone 2 running Android 5.1 and could not reproduce it on a Samsung Galaxy S7. I also seem to be the only one in my social circle that has this problem.
I'm not really an Android developer but in iOS cells from tables (what people at Apple call lists) are reused when scrolling to (I guess) minimize memory allocations. I'm guessing that in Android something similar is done and it seems to fail to update the cells correctly?
Oh, I forgot to add (and can't find an edit button in the mobile version of the github page):
The issue, of course, becomes worse if the keyboard is being displayed, as there is less space. So, when scrolling up, messages are replaced by "already seen" messages from a newer date below earlier.
Not sure if this is helpful. Might be difficult to understand from my explanation. If necessary, I can try to provide screenshots.
@tsdmgz Thank you so much! That's really helpful. I don't totally understand what's wrong with my change, but it does seem like the culprit. I will probably just revert it.
in 3.30.0
Tested and working. Thank you @moxie0!
@r-arias
If you can do a backup from Titanium Backup, try testing this out.
I don't build from source but would have no problem testing, although it seems to have been fixed. I will just wait for the update to hit the play store. Thank you so much to everyone who reported and helped fix this issue!