When I stop the gateway and start the gateway again, I need to also restart the app once, because no message is send out anymore (only sendin.. status and when the app is closed and restarted, the message I wrote is gone)
Expected behavior:
When the gateway restarted, and the app is connected, the message should be sent.
When the gateway restarted and the app is not directly connected, queue the message and send it as soon as it get's connected.
When I stop the gateway and start the gateway again, I need to also restart the app once, because no message is send out anymore (only sendin.. status and when the app is closed and restarted, the message I wrote is gone)
Expected behavior:
When the gateway restarted, and the app is connected, the message should be sent.
When the gateway restarted and the app is not directly connected, queue the message and send it as soon as it get's connected.
Pakobbix
added the bug label 2026-08-22 22:38:49 +00:00
ARIA
was assigned by Pakobbix2026-08-22 22:38:49 +00:00
Pakobbix
added this to the version 1.0 project 2026-08-22 22:38:49 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When I stop the gateway and start the gateway again, I need to also restart the app once, because no message is send out anymore (only sendin.. status and when the app is closed and restarted, the message I wrote is gone)
Expected behavior:
When the gateway restarted, and the app is connected, the message should be sent.
When the gateway restarted and the app is not directly connected, queue the message and send it as soon as it get's connected.