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

Sometimes no history is retrieved if join public chat #7282

Closed
annadanchenko opened this Issue Jan 15, 2019 · 5 comments

Comments

Projects
None yet
3 participants
@annadanchenko
Copy link
Member

annadanchenko commented Jan 15, 2019

Description

Type: Bug

Summary: Sometimes if join public chat there is no history retrieved (stable wifi connection, even if there is history, even if use "Fetch last 24 hours", on mailserver that works fine)

Found on today's 0.9.33 nightly + staging fleet or on default beta fleet and same nightly

Expected behavior

last 24 h messages are shown in public chat

Actual behavior

No messages is shown for the chat (even if it has some)

Reproduction

I can't reproduce it constantly but if try these steps 3-4 times you might be lucky:

  1. create new account
  2. add picture to profile (to allow access to Storage)
  3. change fleet to staging
  4. log in
  5. join "status" or "status-core" chat and check if history is retrieved
    If relaunch app and log in then history is retrieved fine

I don't think it's because of mailserver. When no messages were retrieved there was "mail-01.do-ams3.eth.staging" mailserver. I've killed and started the app again, other mailserver was selected and history was retrieved. Then I've manually selected "mail-01.do-ams3.eth.staging" and joined another public chat - history is retrieved fine.

Additional Information

  • Status version: 0.9.33 (2019011503) status-go v0.17.11-beta.e081f3ec
  • Operating System: Android 6.0.1 real Galaxy S6 device

Logs

For staging fleet:
Status.log
geth.log

For beta fleet:
geth.log
Status.log

@cammellos

This comment has been minimized.

Copy link
Member

cammellos commented Jan 16, 2019

Looking into this, checking the logs one thing that can be noticed is that the public-chat was joined before the mailserver was ready (that would explain why it only happens sometimes), but will check to validate that.

@annadanchenko

This comment has been minimized.

Copy link
Member Author

annadanchenko commented Jan 16, 2019

using debug PR #7285 can reproduce on Android build (real Galaxy S6, Android 6.0.1)

modified steps:

  1. create new account
  2. add picture to profile (to allow access to Storage)
  3. Log out
  4. log in
  5. join "status" or "status-core" chat and check if history is retrieved

Status.log
geth.log

@churik

This comment has been minimized.

Copy link
Member

churik commented Jan 16, 2019

@cammellos tested 0.9.32 release build on eth.staging fleet and some messages are not fetched when you go back from offline.
Steps to reproduce:

  • close app
  • send ~10 messages in different chats from another device
  • open app and log in
  • wait 2+ mins for messages to fetch

Expected result: all messages are fetched
Actual result: none of the messages are fetched
Reproducible almost every time.
Sometimes messages are fetched after switching to eth.beta, but not every time.
Logcat: logcat-andr.txt

I believe, the reason can be similar, so I've put it as comment. If it is completely different, let me know and I'll create separate issue.

NOTE: it is not reproducible if you have selected eth.beta before closing app (5\5 times)

@cammellos

This comment has been minimized.

Copy link
Member

cammellos commented Jan 16, 2019

@churik would you mind using the test build from #7285 and replicate? thanks!

@churik

This comment has been minimized.

Copy link
Member

churik commented Jan 16, 2019

@cammellos can't reproduce #7282 (comment) on #7285 on eth.staging. Tried around 10 times with different chats number, mailservers and network - no success

UPD: can't reproduce #7282 (comment) as well on eth.staging + 0.9.32, tried around 10 times.

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