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 Nov 25, 2022. It is now read-only.
Not sure if this is a desktop, a node-bindings or a core issue:
When I track the events that are emitted when receiving a new message in deltachat_desktop I see only DC_EVENT_MSGS_CHANGED but not DC_EVENT_INCOMING_MSG
If I call dc_get_fresh_msgs immediately after receiving the message the number of fresh messages is not increased. I see the new message in the database and it is has state 26 instead of 10...
When new messages are received during desktop being closed they have the correct state in database (which indicates that the error might be in desktop) but nevertheless the DC_EVENT_INCOMING_MSG should be emitted before anything else happens...
The text was updated successfully, but these errors were encountered:
Not sure if this is a desktop, a node-bindings or a core issue:
When I track the events that are emitted when receiving a new message in deltachat_desktop I see only DC_EVENT_MSGS_CHANGED but not DC_EVENT_INCOMING_MSG
If I call dc_get_fresh_msgs immediately after receiving the message the number of fresh messages is not increased. I see the new message in the database and it is has state 26 instead of 10...
When new messages are received during desktop being closed they have the correct state in database (which indicates that the error might be in desktop) but nevertheless the DC_EVENT_INCOMING_MSG should be emitted before anything else happens...
The text was updated successfully, but these errors were encountered: