# Telegram app unexpectedly stopped

**URL:** <https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577>\
**Category:** Apps\
**Created:** [September 1, 2019, 9:05am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577 "2019-09-01T09:05:05Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tupangitim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tupangitim/32/941_2.png) [@Tupangitim](https://community.homey.app/u/Tupangitim)\
**Post date:** [September 1, 2019, 9:05am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/1 "2019-09-01T09:05:05Z")

</div>

Hi guys,

Need help. My telegram always having error.

See picture below.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/f/f3bcd2bc09b285f748b3ad4321d732f56a2d680f.jpeg)

---

<div class="post-metadata">

**Author:** ![Eternity](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eternity/32/102113_2.png) [@Eternity](https://community.homey.app/u/Eternity)\
**Post date:** [September 1, 2019, 9:30am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/2 "2019-09-01T09:30:25Z")

</div>

I have the same since a couple of days:

 ![Screenshot_20190901-112757](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/8/87d280f1bd9fba5d1907cc74774624deca697488.jpeg)

I made a flow to restart the app after a crash, but would prefer a real solution 😁

---

<div class="post-metadata">

**Author:** ![Eternity](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eternity/32/102113_2.png) [@Eternity](https://community.homey.app/u/Eternity)\
**Post date:** [September 1, 2019, 9:38am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/4 "2019-09-01T09:38:11Z")

</div>

Well, no. The developer was notified by Homey.

---

<div class="post-metadata">

**Author:** ![Tupangitim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tupangitim/32/941_2.png) [@Tupangitim](https://community.homey.app/u/Tupangitim)\
**Post date:** [September 1, 2019, 10:08am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/6 "2019-09-01T10:08:39Z")

</div>

Please share your flow.

Thank you

---

<div class="post-metadata">

**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\
**Post date:** [September 1, 2019, 10:29am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/7 "2019-09-01T10:29:34Z")

</div>

Developer is notified via gh issues, is mentioned in Slack and pm is sent also in Slack. Then he gets several emails from users automagically so he should know by now.

---

<div class="post-metadata">

**Author:** ![Eternity](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eternity/32/102113_2.png) [@Eternity](https://community.homey.app/u/Eternity)\
**Post date:** [September 1, 2019, 10:55am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/9 "2019-09-01T10:55:47Z")

</div>

@Tupangitim

Sure! Here you go:

 ![53](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/3/33ce69aa189512dffeb298b6a3eb1ccd899ea29f.jpeg)  
I added the delay to avoid a crash loop, which in return might cause Homey to stop responding

@RoyWissenburg  
The benefit of posting this issue on the forum is that others might have a solution or workaround. Also, it is good to read that 'I am not the only one" with that issue. And, also, now other with the same issue are informed that indeed the developer has been notified via other channels (slack and gh issues).

---

<div class="post-metadata">

**Author:** ![Tupangitim](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tupangitim/32/941_2.png) [@Tupangitim](https://community.homey.app/u/Tupangitim)\
**Post date:** [September 1, 2019, 11:45am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/10 "2019-09-01T11:45:18Z")

</div>

Wait, i dont have this option on the flow.

How to get system on the flow?

---

<div class="post-metadata">

**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\
**Post date:** [September 1, 2019, 11:48am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/11 "2019-09-01T11:48:28Z")

</div>

Enable power user in settings/experiments

---

<div class="post-metadata">

**Author:** ![khangwei](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/khangwei/32/9687_2.png) [@khangwei](https://community.homey.app/u/khangwei)\
**Post date:** [September 1, 2019, 12:32pm UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/12 "2019-09-01T12:32:35Z")

</div>

mine stopped working too

---

<div class="post-metadata">

**Author:** ![CorvanderNiet](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/corvanderniet/32/11702_2.png) [@CorvanderNiet](https://community.homey.app/u/CorvanderNiet)\
**Post date:** [September 2, 2019, 7:37am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/13 "2019-09-02T07:37:28Z")

</div>

Strange. I had a crash every 6-10 hours. Yesterday afternoon I restarted Homey itself. No more crashes since then … so far

EDIT: that only helped for 26 hours.

---

<div class="post-metadata">

**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\
**Post date:** [September 2, 2019, 9:10am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/14 "2019-09-02T09:10:45Z")

</div>

Just talked to the developer. He just got back from his vacation and is going to look into it. No ETA.  
For now just try a restart of the app itself and let us know ur findings.

---

<div class="post-metadata">

**Author:** ![CorvanderNiet](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/corvanderniet/32/11702_2.png) [@CorvanderNiet](https://community.homey.app/u/CorvanderNiet)\
**Post date:** [September 3, 2019, 11:01am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/15 "2019-09-03T11:01:04Z")

</div>

3 crashes in one hour and an interesting discussion going on at GitHub. I think (hope) we’re getting closer to a solution. Go for it developers!

---

<div class="post-metadata">

**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\
**Post date:** [September 3, 2019, 11:55am UTC](https://community.homey.app/t/telegram-app-unexpectedly-stopped/17577/16 "2019-09-03T11:55:29Z")

</div>

Issue can be monitored here: [https://github.com/jordenc/org.telegram.api.bot/issues/34](https://github.com/jordenc/org.telegram.api.bot/issues/34)

TLDR:

Seems data from one user was sent to all users of the Telegram App and crashed that because of invalid formatted data.  
The user who’s data it concerned has reported this at the Dutch Autoriteit Persoonsgegevens and will turn this into a complaint when it’s not resolved to his satisfaction.  
Athom has fixed the data leak on their end, no official report yet.

To be continued…
