Scrolling returns to the end of chat instead of scrolling up to the previous messages on Android 9

[annadanchenko]

Description

Type: Bug

Summary: only on Android 9 (can't repro on 6 and 7):
Scrolling up (touch screen, move finger down, remove finger from the screen) does not go up in the chat (public or 1:1) instead you see end of the chat with most recent messages. It works only if you scroll up with 2 fingers and each moment one of fingers touches the screen, as soon as no fingers are touching the screen you go back to the end of chat or remain in position where you've moved finger away from the screen.

Expected behavior

Can scroll messages in the chat up and down

Actual behavior

If scroll up and remove finger from the screen - end of chat is shown instead of scrolling up to previous messages

Reproduction

• Open Status public chat or any other 1:1 or public chat with messages
• Scroll up to see Yesterday's messages

Additional Information

• Status version: nightly from Aug 16 http://artifacts.status.im:8081/artifactory/nightlies-local/im.status.ethereum-31924f-n-fl.apk and https://i.diawi.com/ynGb9s
  version 0.9.26 (6406) node a6d69ed
• Operating System: real Pixel XL (Android 9).
  Can't reproduce on real Galaxy S6 with Android 6.0.1 and on real Xiaomi Redmi 4 wtih Android 7

Logs

Tf session: https://app.testfairy.com/projects/4803622-status/builds/8559654/sessions/4398732690/?accessToken=Qv-2PggPzX5DMAz-ZJYwjIx6P-g

Install - Diawi - Development and In-house Apps Wireless Installation

TestFairy: Status 0.9.26 (6406) @2018

[lukaszfryc]

@jpbowen has just reproduced this issue on his phone. It totally broke his experience. I think we should fix it asap since more and more people are upgrading to Android 9.

[mandrigin]

RN issue: facebook/react-native#19434

[mandrigin]

Android 9 issue: https://issuetracker.google.com/issues/112385925

Sign in - Google Accounts

[mandrigin]

Workaround in our fork:
status-im/react-native#1

[mandrigin]

Workaround in RN: facebook/react-native#21117

[mandrigin]

Merged the workaround, it should fix the issue