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

New message do not appear if app is open #27

Closed
klaszlo opened this issue Feb 5, 2017 · 30 comments
Closed

New message do not appear if app is open #27

klaszlo opened this issue Feb 5, 2017 · 30 comments
Labels
Milestone

Comments

@klaszlo
Copy link

klaszlo commented Feb 5, 2017

I tested on two phones (sony android 5.1.1, oneplus android 5.1.1), both
application is downloaded via f-droid (v0.1.15, 2/2/2017).

I added two gmail account, enabled less secure app login inside gmail, I rebooted both phone.
The problem is, if I send a message, on the other phone it do not appear until I close
delta chat, after closing in 2-5 sec and a new notification appear.
If I leave open the delta chat's chat window, the new message never arrives.

In the gmail account the message is properly sent and received.
As a workaround it would be nice to have a manual refresh icon inside chat window.

@rsajdok
Copy link

rsajdok commented Feb 12, 2017

I have the same problem. Only after restart app I can see the new messages.

@Szaman1701
Copy link

Got the same issue, Im on Huawei 8P lite with android 6.0. I can freely send a messages, but for some reason app doesn't download responses from my mailbox, despite the fact that I got them and can read them via mail app.

@ttandej
Copy link

ttandej commented Feb 14, 2017

I have the same issue, but I have found that it only seems to affect Gmail. I have a gnspes mail and it updates perfectly.

@r10s r10s added the bug label Feb 16, 2017
@r10s
Copy link
Member

r10s commented Feb 16, 2017

As this seems only to affect Google, this issue should be fixed by deltachat/deltachat-core@b711919

If the problem is still present in the upcoming release (v0.1.20 or later), please re-open this issue. For now, it is closed.

See also issue #44.

@r10s r10s closed this as completed Feb 16, 2017
@klaszlo
Copy link
Author

klaszlo commented Feb 24, 2017

after updating to v0.1.20 (f-droid repository). The exact same bug remains.
The other side do not receive my chat, and me neither hers.

Delta chat was updated on both end.

@klaszlo
Copy link
Author

klaszlo commented Feb 24, 2017

this issue can only be reopened by @r10s .

@r10s
Copy link
Member

r10s commented Feb 27, 2017

Okay, we will check this again; any further information are welcome.

@r10s r10s reopened this Feb 27, 2017
@klaszlo
Copy link
Author

klaszlo commented Feb 27, 2017

@r10s: first comment still holds:

  • when I close the app via the android app switcher, I get the notification within a moment.
  • the message do arrive inside the gmail account.
  • the "mailbox" inside the app, is also unreliable.
  • the same error/symptom on both phone (sony z1compact, android 5.1.1 factory version, oneplus android 5.1.1)

@zoff99
Copy link

zoff99 commented Apr 10, 2017

+1
this is still happening on the latest playstore version

i am not using a gmail account for this

@r10s
Copy link
Member

r10s commented Apr 11, 2017

this is still happening on the latest playstore version

I think you're talking about the F-Droid-version?!

@zoff99
Copy link

zoff99 commented Apr 11, 2017

@r10s sorry, yes. f-droid version. will the f-droid version be fix aswell?

@r10s
Copy link
Member

r10s commented Apr 11, 2017

@r10s sorry, yes. f-droid version. will the f-droid version be fix aswell?

Yes. In fact, F-Droid ist the main distribution channel for the moment.

@zoff99
Copy link

zoff99 commented Apr 11, 2017

ok. so now i am confused. should it be already solved in the latest f-droid version or not yet?

@r10s
Copy link
Member

r10s commented Apr 11, 2017

Well, I don't know if it works. I only know there were massive changes, esp. regarding google. I have no problems with Google and with my other testing accounts - otherwise I would fix them ;-)

(the most recent version released is 0.1.25 which is available on F-Droid, the only release channel at the moment, to be sure, no old stuff in the database, it may be an good idea to deinstall and reinstall the app (normally, this is not carry-on, but, who knows ...))

@zoff99
Copy link

zoff99 commented Apr 12, 2017

well. i dont understand what you are saying exactly.
anyway, this bug is still there.

@tbart
Copy link

tbart commented Apr 25, 2017

I can confirm this bug on lineageos 14.1 (Android 7.1.2) on a Nexus 5 using gmx.at and 0.1.32 from f-droid.org.
If I test deltachat with a second phone (exactly the same specs) it works - mostly that is (phones are either turned on or put to sleep a minute ago)
If I send a message a day later with the second phone being turned on currently or having opened deltachat recently, the messages do not show up in deltachat. They always get sent, as I see them in the web mail interface.
Restarting the app always helps as messages get downloaded again.
Sometimes messages magically appear hours or even days later.
It somehow seems the IMAP connection gets dropped in the background. However, K9-Mail works perfectly using IMAP-Push.
Can you offer some debug build or is there anything we can look for in logcat to help you dissect this bug?

@r10s
Copy link
Member

r10s commented Apr 29, 2017

There is no official debug version, but the Delta Chat log is very detailed. You can inspect it using the usual logcat tools.

@dezifit
Copy link

dezifit commented Jul 18, 2017

Same issue with current version (v0.9.2) and provider Unitymedia. Tested with older Cyanogen 5.1.1, see attached logcat excerpt. Anything I can do or test?
logcat.txt

@r10s r10s added this to the Version 1.0.0 milestone Dec 20, 2017
@testbird testbird removed this from the Release 1.0 milestone Mar 4, 2018
@r10s r10s added this to the Release 1.0 milestone Mar 5, 2018
@t-oster
Copy link

t-oster commented Jun 7, 2018

@dezifit is the bug still on the current versio n?

@csb0730
Copy link

csb0730 commented Jun 8, 2018

@t-oster , @dezifit ,

I tested with v0.17.3.
New message appears under all conditions:

  • only app open (chat list)
  • I'm in another chat
  • I'm in the chat where the message is intended for.

Contact Request excluded here because anyway no alert.

So I think issue can be closed

@t-oster
Copy link

t-oster commented Jun 8, 2018

ok if @klaszlo and @zoff99 did not experience something different we should consider this solved.

@testbird
Copy link

testbird commented Jun 8, 2018

I tried to reproduce with just one phone by using a MUA and copying old emails from a chat contact (from before deltachat even existed) into the INBOX on the server and setting them as "unread", but the messages did not even appear in DC.

It worked though with a message I sent myself (appeared on the right side)

@dezifit
Copy link

dezifit commented Jun 8, 2018

I reinstalled Delta-Chat and created a test group with 2 members. I used the standard group creation notification as test message, which was send as expected to the group participant, a standard mail account.

After receiving this notification mail I used Thunderbird to reply it, but the reply isn't shown in delta-chat. I verified with the web interface of the mail account used by delta-chat and the reply is visble/waiting in the inbox (with usual subject "Re: chat: ..."). So no, if I didn't made a stupid error, it still doesn't work.

@t-oster
Copy link

t-oster commented Jun 8, 2018

could you provide the log and the mail headers of the reply email?

@t-oster
Copy link

t-oster commented Jun 8, 2018

is it shown under Kontaktanfragen?

@dezifit
Copy link

dezifit commented Jun 8, 2018

No, nothing shown in "Kontaktanfragen".

@testbird
Copy link

testbird commented Jun 8, 2018

I tried to reproduce with just one phone by using a MUA and copying old emails from a chat contact (from before deltachat even existed) into the INBOX on the server and setting them as "unread", but the messages did not even appear in DC.

It worked though when I copied an old a message that I had sent myself (it appeared on the right side).

@csb0730
Copy link

csb0730 commented Jun 8, 2018

Ok a short illustration of my test:

  • I used an existing (single) chat for testing
  • I sent three new (!) messages to the chat

I think both circumstances are important because otherwise some more difficulties are playing into this game!

  1. I made the experience that a mailserver doesn't show old messages for a client. This is not a DC's problem, more a mail server issue. But You should pay attention to that.
  2. If You are trying to sent to a "group" then more difficulties in mapping messages to a group are relevant too. See the issues (core 68, 69 or even Introduce a function to move (not forward) a message to another chat at local device  #324) which are reflecting these problems.
  3. See imap logging at settings->Info->Info. There You can see what (if at all) DC is doing. Maybe You see there a hint if DC sees, downloads or ignores the certain message if You make the try.

I hope this helps

@testbird
Copy link

testbird commented Jun 9, 2018

In the log I can see that (some days? due to reasons unknown to me) the "IDLE interrupted" appears every half hour. But I would still expect the old message copy to be displayed after the half hour.

I made the experience that a mailserver doesn't show old messages for a client. This is not a DC's problem, more a mail server issue.

What do you mean by "mailserver doesn't show for a client"? How could you determine that?
My old message sent by myself did show up properly, when copied to the inbox.

Could you try copying old messages from a local archive to the server?
(After a while, flag them to unread again, I think that may be another issue, still.)

@r10s
Copy link
Member

r10s commented Jul 10, 2018

i think most of these issues are targeted by the changes to the imap-jobs in v0.18.0 and newer versions.

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