Skip to content
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

Slow update of chat messages ( Suspected 163mail provider problem ) #2579

Closed
fengguowudi opened this issue Feb 3, 2025 · 2 comments
Closed
Labels

Comments

@fengguowudi
Copy link

  • iOS version: 14.4
  • Device: iPhone 7 Plus
  • Delta Chat version: 1.52.2
  • Expected behavior: Receive messages in a timely manner
  • Actual behavior: It takes a very long wait to receive the message. Sometimes you can't even get a message. You need to restart the app to receive messages.
  • Steps to reproduce the problem:
    1.Use 163 mail as the service provider for the test subject.
    2.Send a message to the collaborator. The collaborator receives the message within 5 seconds and immediately replies. The reply contains the current time.
    3.On the test subject's client, observe the situation: if no reply is received for more than 10 minutes, check 163 mail. The reply is already in the folder there, but the INBOX in the client has not refreshed. Forcefully clear the background processes and restart the Delta Chat application to receive the message sent by the collaborator.
  • Screenshots:

Image

Image

  • Logs:
**This log may contain sensitive information. If you want to post it publicly you may examine and edit it beforehand.**

iosVersion=14.4
any-database-encrypted=false
notify-token=<unset>
backgroundRefreshStatus=available
DEBUG=0

arch=64
authserv_id_candidates=gzga-mx-mtada-g8-8
bcc_self=1
blobdir=
bot=0
configured_inbox_folder=INBOX
configured_mvbox_folder=DeltaChat
configured_sentbox_folder=
configured_trash_folder=
database_dir=
database_encrypted=false
database_version=129
debug_logging=0
delete_device_after=0
delete_server_after=0
delete_to_trash=<unset>
deltachat_core_version=v1.155.2
disable_idle=false
displayname=
download_limit=0
e2ee_enabled=1
entered_account_settings=
fetch_existing_msgs=0
fetched_existing_msgs=true
fingerprint=
fix_is_chatmail=false
folders_configured=5
gossip_period=172800
imap_server_id={"TransID": "", "vendor": "Mailtech", "name": "Coremail Imap"}
is_chatmail=false
is_configured=1
is_muted=false
journal_mode=wal
key_gen_type=0
last_cant_decrypt_outgoing_msgs=0
last_housekeeping=1738552753
last_msg_id=430
level=awesome
mdns_enabled=1
media_quality=0
messages_in_contact_requests=0
mvbox_move=1
num_cpus=2
number_of_chat_messages=90
number_of_chats=4
number_of_contacts=100
only_fetch_mvbox=0
private_key_count=1
private_tag=<unset>
protect_autocrypt=0
proxy_enabled=0
public_key_count=3
quota_exceeding=0
save_mime_headers=false
scan_all_folders_debounce_secs=60
secondary_addrs=
selfavatar=<unset>
sentbox_watch=1
show_emails=0
sign_unencrypted=0
sqlite_version=3.45.3
sync_msgs=1
uptime=0h 0m 24s
used_account_settings=
verified_one_on_one_chats=true
webrtc_instance=<unset>
webxdc_realtime_enabled=true

notify-timestamps=1月 7, 2024, 11:55 上午 1月 7, 2024, 12:04 下午 
notify-fetch-info=
[06:48 上午] ▶️ ▶️ ⏸️ 
[03:30 下午] ▶️ ▶️ ⏸️ 
[07:59 下午] ▶️ ▶️ ⏸️ 
[08:00 下午] ▶️ ▶️ ⏸️ 
[10:08 上午] ▶️ ▶️ 
[10:09 上午] ⏸️ 
[07:52 下午] ▶️ ▶️ 
[07:54 下午] ▶️ ▶️ 
[07:55 下午] ⏸️ ▶️ ▶️ 
[07:56 下午] ▶️ ▶️ 
[07:59 下午] ▶️ ▶️ 
[08:00 下午] ⏸️ 
[08:04 下午] ▶️ ▶️ 
[08:08 下午] ⏸️ ▶️ ▶️ 
[08:10 下午] ▶️ ▶️ ⏸️ ▶️ ▶️ 
[08:13 下午] ▶️ ⏸️ ▶️ ▶️ 
[08:14 下午] ⏸️ ▶️ ▶️ ⏸️ ▶️ ▶️ ⏸️ ▶️ ▶️ ⏸️ ▶️ ▶️ ▶️ ▶️ ⏸️ ▶️ ▶️ 
[08:15 下午] ⏸️ 
[08:23 下午] ▶️ ▶️ 
[08:24 下午] ⏸️ 
[08:25 下午] ▶️ ▶️ ⏸️ 
[11:08 上午] ▶️ ▶️ 
[11:10 上午] ▶️ 
[11:12 上午] ▶️ 
[11:17 上午] ▶️ 
[11:19 上午] ▶️ 
[11:24 上午] ▶️ 
[11:34 上午] ▶️ ▶️ ▶️ ▶️ ⏸️ ▶️ ▶️ 
[11:49 上午] ⏸️ ▶️ ▶️ 
@fengguowudi fengguowudi added the bug label Feb 3, 2025
@r10s
Copy link
Member

r10s commented Feb 3, 2025

can you post the full log?

there should be sth below the ⏸️ ▶️ program-start-emoji -- at least a hint where to get the full log

but the INBOX in the client has not refreshed. Forcefully clear the background processes and restart the Delta Chat application to receive the message sent by the collaborator.

to exclude it is an ui issue: if it happens again, and you enter flighr mode before reatarting the Delta Chat application - are the messages shown then?

@r10s
Copy link
Member

r10s commented Feb 13, 2025

closing as there is no actionable item. it is very likely not an UI issue and a - maybe fitting - core issue references this issue

@r10s r10s closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants