Closed Hocuri closed 4 years ago
Might be the same as https://github.com/deltachat/deltachat-android/issues/1427
2020-06-19 16:30:33.984 7050-7050/? I/DeltaChat: ++++++++++++++++++ first ForegroundDetector.onActivityStarted() ++++++++++++++++++
2020-06-19 16:30:33.984 7050-7050/? I/DeltaChat: ++++++++++++++++++ ApplicationDcContext.maybeStartIo() ++++++++++++++++++
2020-06-19 16:30:33.986 7050-7116/? I/DeltaChat: calling maybeNetwork()
2020-06-19 16:30:33.987 7050-7116/? I/DeltaChat: maybeNetwork() returned
2020-06-19 16:30:34.046 7050-7050/? I/DeltaChat: ++++++++++++++++++ Connected ++++++++++++++++++
2020-06-19 16:30:34.047 7050-7050/? I/DeltaChat: *** KeepAliveService.onCreate()
2020-06-19 16:30:34.048 7050-7130/? I/DeltaChat: calling maybeNetwork()
2020-06-19 16:30:34.048 7050-7130/? I/DeltaChat: maybeNetwork() returned
2020-06-19 16:30:34.052 7050-7050/? I/DeltaChat: *** KeepAliveService.onStartCommand()
No idea if this https://github.com/deltachat/deltachat-ios/pull/786 has to be done in the deltachat-android branch, too. Edit: Oops, sorry, I have recognized that the network check is already done conditionally on Android...
Not sure what is going on here as the move to async lost us some logging-context (which folder imap operations happens on). The log says:
2020-06-19 16:30:35.107 7050-7088/? I/DeltaChat: src/imap/mod.rs:699: fetch_new_messages: ignoring uid 5134, last seen was 5134
2020-06-19 16:30:35.107 7050-7088/? I/DeltaChat: src/imap/mod.rs:649: 0 mails read from "DeltaChat".
2020-06-19 16:30:35.146 7050-7088/? I/DeltaChat: src/imap/mod.rs:699: fetch_new_messages: ignoring uid 1056, last seen was 1056
2020-06-19 16:30:35.146 7050-7088/? I/DeltaChat: src/imap/mod.rs:649: 0 mails read from "Gesendet".
2020-06-19 16:30:35.186 7050-7088/? I/DeltaChat: src/dc_receive_imf.rs:46: Receiving message INBOX/10590...
And i wonder where this UID INBOX/10590 suddenly comes from.
What's your provider? What's your watch-settings? do you move messages?
FWIW i suspect that core still has a problem to remain alive by itself (i.e. continue to receive messages). I have a 29h uptime with DC on my phone, and it happened today often that only when i brought DC to the front do messages flow in (it's fast, but clearly only happens then). I even was in the same WLAN for many hours i think. This might be a different issue than the one reported here, not sure.
What's your provider? What's your watch-settings? do you move messages?
GMX, watch all three, yes (but the non-arriving messages stayed in the inbox first. They were only moved after force-stopping DC, when they also arrived in DC.)
I think we can close this, it did not happen again.
After swiping away:
After force stop: