Signal terminates after update. #13697
Comments
|
This is happening for me since a few days, too. Seems to be the same bug: I have hundreds of these crashes and it's impossible to open signal for longer than a second without it closing on me. Also happening on 7.17.4, but I installed the apk from the webpage in the hopes of making things better with that - it might have been a different version before that. |
|
same here with 7.17.4. and 7.17.5. |
|
this has been going on for 3 days. currently I have 7.17.5, updated today |
|
Same here. I was hopeful seeing the Signal 7.17.5 update so soon after 7.17.4 (which seemingly was the on that broke everything), but still no go. Interestingly (or at least potentially so), the update notification for 7.17.5 came, even though the download didn't work. (I'm on microG, no Google Play, so I'm assuming Signal is continually updating itself directly from the Signal website?) I've used Signal for nearly 9 years and I have a comprehensive history of messages and media on my phone. I would find it quite distressing if there weren't a way out of this situation. In my case, the logcat errors (that I could see as being relevant) were these: |
|
Also happening to me with 7.17.5 as of today, Sep 20 2024. |
|
@tbcx there's fixes for this crash coming in 7.18 |
|
@greyson-signal unfortunately, they seem to have a different crash than the rest of us - did you have a chance to look into the crash initially reported here ( In the meantime: is downgrading an option? I haven't been able to use a messenger in a week :/ |
|
I have the same crash since updating to 7.17.5. ( |
|
Same issue here since upgrade to 7.17.5 yesterday [Galaxy S10, Android 12]: Unable to open Signal, crashes under 1sec once I try. |
|
I had the same symptoms since the 7.17.5 update. Deleting the app cache fixed it apparently, for now at least. |
|
Got the update to 7.17.5 today and started seeing the same crash ( |
|
@haffenloher Interesting find, this behaviour is also true on my FP4 (Android 14, microG). I just need to let it crash a certain amount and now I can start Signal... crazy. Btw. the crash started with the 7.17.5 update. |
|
I can confirm this. The magic 'certain amount' was 153 for me. |
|
Good morning! I upgraded to Signal 7.17.5 today and ran into the same issue as OP. Opening the Signal app caused it to show my conversations for a few frames and immediately crash with Thank you to @haffenloher for a workaround and to @Diapolo and @vbartik for sharing that it worked for you, it worked for me as well! Idk how many times I opened it debugging or how many times it has been crashing in the background, but I tapped the Signal icon about a dozen times in a row and it stopped crashing. Feels a little sluggish but it works for me. I find it interesting that @tbcx is using MicroG and has a very long history. I am also using MicroG (specifically their Lineage fork), I install Signal using the Aurora Store client for Google Play, I have a very old history going back to at least 2015-06-14, and my backups are ~14 GB of mostly text. I wonder if anyone else having this issue is using MicroG, has a very old history, or both. LogcatTaken with LogFox using root while Signal was still crashing. This is an excerpt, but I have the entire syslog saved and will share it with the Signal Foundation upon request. You can see it crashes on attachment 81, then attachment 82, then attachment 83. I am open-minded to sharing these attachments with the Signal Foundation for debugging or a test case, depending what they are, if you can help me identify and export them. Signal Debug LogThe Signal > Settings > Help > Debug Log is attached. Thank you for the work you guys do, let me know if I can help debug. |
|
@kj4ezj My history is also very old, 2013 and below. My backups are ~6 GB in size. Not sure if this crash-start-workaround is breaking other stuff? |
|
I'm also having a very old history, >10 years, and I have some groups that crash Signal when I try to look at the corresponding message of some old media.
I've tried them until viewing doesn't crash anymore and if I scroll further into the past, the same happens. |
|
IIUC that should be the Exception |
First of all, I didn't know you could click the date there and jump to the message...do you know how long I have wanted that, wondered why it isn't there, and how much time it would have saved me?!?!? Thanks a ton, haha. Anyways, I was not able to replicate your bug. It is hard to find such old media in buried threads, but I tried your steps using group chat photos as old as 2016-06-20 and DMed photos as old as 2015-06-03. |
So, there was really no reason to expect that the 7.17.6 release would fix this, and I didn't really, but I had to try anyway (nothing to lose!) and as expected. 7.17.6 still crashes Signal before I can finish typing my password. Fingers crossed for 7.18! |
4 tasks
|
It does indeed stop crashing after opening it many times in a row, but now I have no option to unlock the app (I enabled screen lock). Tapping on the "unlock" button does nothing. It seems that the workaround does not work for everyone :/. I hope 7.18 is rolled out quickly, as Signal is my main messenger application. |
|
Same here, BUT in my case (and maybe in case of a portion of others as well), it doesn't crash if I am fast enough to click open a chat, instead it BACKS OUT of the chat and the app. If I am fast enough, I can keep up with Signal dance and keep re-entering settings or chats in turn with Signal doing "one step back" every half second or so. Only when I stop has Signal enough time for two consequent back steps leading to backing out of the app (not crashing). If I don't engage in this dance at all, then it crashes within less than a second after launching. |
|
Actually, I still don't have 7.18 rolled out for me, but after a few more tries when this first happened, I could get the unlock function to work and as a quick fix I have disabled app locking in Signal. My thought was that this could give me a working app by opening it just often enough once this would happen the next time. I don't think this needs more debugging. As a fix is already scheduled, the root cause is likely already identified. But maybe this comment can help others who experience the same issue. |
|
7.18.2 downloaded from the website, and it works. My phone is Signal-capable again. I'm delighted, and so incredibly, incredibly relieved. Much thanks to the Signal developers for coming through. |
|
I also got the 7.18.2 update via the Play Store, but sadly it did not solve the originally reported crash ( |
|
I just updated to 7.18.2 and the problem persists. This phone is a Samsung S7 with Android 8.0.0. |
|
Same, no luck after last update. OnePlus 9 Pro with Android 14. |
That's also the behavior I tried to describe in the initial report. And just FTR I have another phone that just updated to 7.18.2 and the problem persists. Also the workaround to restart Signal until it started again worked in this case. |
|
Is there an update if version 7.19.1 solves this issue? I'm currently writing emails instead of using Signal. |
|
As a workaround I managed to connect Signal to the desktop app before crashing. For that I scanned to QR code via a QR code reader app, which directly opens the signal sync page. |
If this really works there must be something more to the recipe. I have made a Tasker script to launch crash Signal hundred times in a row and it didn't change anything and the crashing persists. |
|
@RadekPilich For me it was significantly more than 100 tries, maybe you can run your script at least 3-4 times? Really confusing issue and workaround though. |
|
@greyson-signal I installed 7.19.2 and Signal still does not work. Is this a new problem or is this still related? Do you need a new log? Is the suggested fix to start Signal 100 times save for the history? |
|
I originally put the app into deep sleep (or so I thought), but 4 days ago, I started to suddenly receive all the (missed) messages and I could open Signal again. Maybe in the background it was trying the 100 times over and over, and at some point the app started working again. However, today I wanted to quote myself in a conversion and Signal suddenly promted the lock screen. After unlocking and sending the message Signal crashed with the same error (I think). Trying this a second time did not make Signal crash. Here is the debug log: https://debuglogs.org/android/7.19.2/efda837af28f9e6a842e1022cbebd7ccbdb643bcf3584cb68d18f88f5a8f4d73 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
Signal closed itself after opening.
Steps to reproduce
Actual result: Signal opens and then closes.
Expected result: Signal should stay opened.
If I was very fast, I could tap on one of the conversations that is shown and then I could see that Signal doesn't simply terminate, but it looked like the 'back' button is pushed until Signal is closed.
I've tried multiple times and there was an Android error message sometimes, but I couldn't read it.
After some time the issue disappeared and now it works again.
Screenshots
None
Device info
Device: FP5 5G
Android version: 14
Signal version: 7.17.4
Link to debug log
Here's an excerpt of the debug log, if you need the complete log feel free to let me know and I'll provide it to you.
That's the part when the update was installed:
That exception happened multiple times, I've added the first and last occurence here:
The text was updated successfully, but these errors were encountered: