Skip to content
This repository has been archived by the owner on Oct 19, 2022. It is now read-only.

3 Dots behind every message sendet from OX-Coi to Delta Chat #221

Closed
webratte opened this issue Oct 23, 2019 · 8 comments · Fixed by deltachat/deltachat-core-rust#1430
Closed
Labels
bug Something isn't working needs verification Must be tested by a developer, to verify the given problem requested / user report Requested by the community

Comments

@webratte
Copy link

webratte commented Oct 23, 2019

Describe the bug
If I send a message from the OX-Coi Android App to the Delta Chat Android- and Desktop Client I have behind every message 3 Dots [...]

See also the attached screenshots

To Reproduce
Occurrence: always
Steps to reproduce the behavior:

  1. Send a message via OX-Coi Android App and receive this message via Delta Chat client
  2. See what I described

App information (please complete the following information):

  • App version: OX-Coi V. beta-2 (2002) Delta Chat V.0.510.1
  • Delta Chat Core version: I don't know
  • Flutter version: I dont know

Smartphone (please complete the following information):

  • Device: Huawei nova
  • OS: Android 7.0

Additional context
I have no idea is this a OX issue or a Delta Chat issue.

But I'm sure the OX team and the Delta Chat team have to work together and have to keep there clients 100% compatible.
Only if the good boys work together there is a chance against the big players.

I think with Chat over E-mail there is a realistic chance to replace WhatsApp with E-mail ;-)

I also opened a issue for Delta Chat:
deltachat/deltachat-android#1082

ox-coi
Deltachat

@webratte
Copy link
Author

After hours of playing around and reinstalling OX-Coi it seems to work again.

So I will close this issue.
I will test more things. If I will find other things, I will reopen it.

@webratte
Copy link
Author

It seems this happens, if I switch off encryption and only with my GMX Account not with Mailbox.org

@webratte webratte reopened this Oct 23, 2019
@webratte
Copy link
Author

Here are the concerned messages.

One is the sent message from the deltachat folder in the GMX account.
And the other is the received message from the deltachat folder in the mailbox.org account.

messagesGMXtoMAILBOX_ORG.zip

@Boehrsi
Copy link
Collaborator

Boehrsi commented Oct 25, 2019

Thanks for reporting that issues and providing all those details. We will have a look what exactly the problem is.

@Boehrsi Boehrsi added bug Something isn't working needs verification Must be tested by a developer, to verify the given problem requested / user report Requested by the community labels Oct 25, 2019
@webratte
Copy link
Author

webratte commented Oct 25, 2019 via email

Hocuri pushed a commit to deltachat/deltachat-core-rust that referenced this issue Apr 28, 2020
Well... Sometimes: fixes #1429, fixes deltachat/deltachat-android#1082, fixes coi-dev/ox-coi#221

This only works when:
1. The message is long enough (I didn't test the threshold but somewhere from 2 to 16 chars
2. The message does not contain a special character.

Otherwise there is no change at all. So, might be that I forgot a place where changes have to be made.

--

I also tried what happens if I remove one of the changes I made:

If I leave out setting the transfer-encoding:
```
message

--=20
Sent with my Delta Chat Messenger: https://delta.chat
```
(message as shown to the user).

If I leave out changing the footer, my change does not have any effect at all, again.
@Hocuri
Copy link

Hocuri commented May 1, 2020

This is an issue with DC-Core and GMX.

@Boehrsi
Copy link
Collaborator

Boehrsi commented May 5, 2020

Thanks for the additional information, I will double check the general functionality (sending / receiving messages without appended three dots) on one of our testing backends, which normally works fine to ensure no general issue exists.

@Boehrsi
Copy link
Collaborator

Boehrsi commented May 11, 2020

Fixed with the latest app + DCC update. Will be integrated in the next release (beta-7).
The fix is about the general problem, potential provider specific issues will be opened (if they exist) separately. Closing this issue for now.

@Boehrsi Boehrsi closed this as completed May 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working needs verification Must be tested by a developer, to verify the given problem requested / user report Requested by the community
Projects
None yet
3 participants