You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2022. It is now read-only.
Describe the bug
Messages, sent to a COI user, should also be visible in E-Mail client. At the moment it is the case that the messages received by Mail client are empty.
To Reproduce
Occurrence: always
Steps to reproduce the behavior:
Open a new chat or use an existing chat
User A sends a message to user B
User B receives the message in COI
User B opens Mail-Client
Check the received message
Expected behavior
Message should also be visible in received mail
Screenshots
If applicable, add screenshots to help explain your problem.
App information (please complete the following information):
App version: [e.g. 0.4.0]
Plugin version: [e.g. 0.4.0]
Delta Chat Core version: [e.g. 0.40.0]
Flutter version: [e.g. 1.0]
Smartphone (please complete the following information):
Device: iPhone 11 Pro Max, iPhone SE (4")
OS: iOS 13.5
Additional context
Add any other context about the problem here.
On non-COI servers this is the case, on COI-enabled servers messages are moved directly. The AppSuite also hides the folders containing chat messages, as far as I remember.
Since this backend is COI enabled normally all mails are sorted + filtered (so hidden in the web UI). If they were shown before / are shown right now (empty) this probably wasn't intended.
Describe the bug
Messages, sent to a COI user, should also be visible in E-Mail client. At the moment it is the case that the messages received by Mail client are empty.
To Reproduce
Occurrence: always
Steps to reproduce the behavior:
Expected behavior
Message should also be visible in received mail
Screenshots
If applicable, add screenshots to help explain your problem.
App information (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
Internal Bug Tracker.
The text was updated successfully, but these errors were encountered: