Signal-Android
Signal-Android copied to clipboard
signalapp
App always crashes after opening
- [x] I have searched open and closed issues for duplicates
- [x] I am submitting a bug report for existing functionality that does not work as intended
- [x] I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
- [x] This isn't a feature request or a discussion topic
Bug description
App crashes within seconds after opening.
I described the problem in another issue (https://github.com/signalapp/Signal-Android/issues/13183#issuecomment-1734458664). Since it is unrelated I opened a separate issue.
I attached more complete adb logs below.
Steps to reproduce
- Open App
Actual result: The App opens and I can use the app for 1 to 3 seconds (even new messages loading) then the crash occurs Expected result: No crashing
Device info
Device: Oneplus 8 Pro Android version: Oxygen 13.1 (Android 13) Signal version: 6.40.4 beta (originally occurred on 6.33.3 stable)
Link to debug log
Most relevant lines probably:
Message: SQL logic errorMessage: cannot commit - no transaction is active
I also wanted to ask if there is any chance that this gets fixed by an update or if my database is irreversibly corrupted. I'd really like not to lose all my data. I used Signal really since forever. Is there anything I can do? Thanks your work is really appreciated.
I don't know if it helps, but the error in your log is not a corruption issue. At the same time, I have tried recreating the same code path but cannot reproduce it, so it's unclear what's going on her.
You can get a more detailed log by going into airplane mode, go to Settings > Help > Debug log, then press the 3-dot menu to get an option to save the file to disk.
Thanks for your insights. Unfortunately I can't get to the debug log menu entry in time before the app crashes.
Oh really, even in airplane mode? The thing that crashes shouldn't run if you don't have network. Maybe the crash happens somewhere else in that case?
Yes tried that several times. Does not make any difference whether being in airplane mode or not.
Same error started happening to me today - 14.02.2024 Signal starts opening for a moment and after 3 seconds crashes. I don't see any chats however I can get into one by desktop shortcuts accessed on the phone's main screen. In such case I can see messages with the selected person but crash happens after 3 seconds anyway. Running in airplane mode or not makes no difference. I have tried clearing cache too
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
I would like to chime in; just happened today. I have never had this issue beforehand. Android 14, Mi A2 Lite, Lineage OS. It doesn't crash whilst having no network (either in airplane mode or disabling wifi/data). Desktop version running just fine.
Do have logs if needed. Not too sure how to read it myself, but a quick glance seems to show a lot of errors regarding username. Thinking back, I do seem to remember getting prompted yesterday or the day before to select my username - despite having set that a long time ago
I'm really sorry if this is unhelpful, but here is a few lines from the log. Unfortunately, I can't submit from within the app itself hence the issue. Can attach here if need be.
04-15 16:42:47.732 23582 23626 E AndroidRuntime: FATAL EXCEPTION: signal-JobRunner-1
04-15 16:42:47.732 23582 23626 E AndroidRuntime: Process: org.thoughtcrime.securesms, PID: 23582
04-15 16:42:47.732 23582 23626 E AndroidRuntime: java.lang.AssertionError: java.lang.ClassNotFoundException: org.signal.libsignal.usernames.UsernameLinkInvalidLinkData
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.signal.libsignal.internal.FilterExceptions.reportUnexpectedException(FilterExceptions.java:70)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.signal.libsignal.internal.FilterExceptions.filterExceptions(FilterExceptions.java:150)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.signal.libsignal.usernames.Username.fromLink(Username.java:102)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.thoughtcrime.securesms.jobs.RefreshOwnProfileJob.checkUsernameIsInSync(RefreshOwnProfileJob.java:331)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.thoughtcrime.securesms.jobs.RefreshOwnProfileJob.onRun(RefreshOwnProfileJob.java:158)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.thoughtcrime.securesms.jobs.BaseJob.run(BaseJob.java:31)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:86)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:49)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: org.signal.libsignal.usernames.UsernameLinkInvalidLinkData
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.signal.libsignal.internal.Native.UsernameLink_DecryptUsername(Native Method)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.signal.libsignal.usernames.Username.lambda$fromLink$2(Username.java:105)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.signal.libsignal.usernames.Username.$r8$lambda$Vy-A0jS3IXkliPqixjPVRDT50rU(Username.java:0)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.signal.libsignal.usernames.Username$$ExternalSyntheticLambda3.run(R8$$SyntheticClass:0)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: at org.signal.libsignal.internal.FilterExceptions.filterExceptions(FilterExceptions.java:143)
04-15 16:42:47.732 23582 23626 E AndroidRuntime: ... 6 more
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: java.lang.AssertionError: java.lang.ClassNotFoundException: org.signal.libsignal.usernames.UsernameLinkInvalidLinkData
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.signal.libsignal.internal.FilterExceptions.reportUnexpectedException(FilterExceptions.java:70)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.signal.libsignal.internal.FilterExceptions.filterExceptions(FilterExceptions.java:150)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.signal.libsignal.usernames.Username.fromLink(Username.java:102)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.thoughtcrime.securesms.jobs.RefreshOwnProfileJob.checkUsernameIsInSync(RefreshOwnProfileJob.java:331)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.thoughtcrime.securesms.jobs.RefreshOwnProfileJob.onRun(RefreshOwnProfileJob.java:158)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.thoughtcrime.securesms.jobs.BaseJob.run(BaseJob.java:31)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:86)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:49)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: Caused by: java.lang.ClassNotFoundException: org.signal.libsignal.usernames.UsernameLinkInvalidLinkData
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.signal.libsignal.internal.Native.UsernameLink_DecryptUsername(Native Method)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.signal.libsignal.usernames.Username.lambda$fromLink$2(Username.java:105)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.signal.libsignal.usernames.Username.$r8$lambda$Vy-A0jS3IXkliPqixjPVRDT50rU(Username.java:0)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.signal.libsignal.usernames.Username$$ExternalSyntheticLambda3.run(R8$$SyntheticClass:0)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: at org.signal.libsignal.internal.FilterExceptions.filterExceptions(FilterExceptions.java:143)
04-15 16:42:47.733 23582 23626 E SignalUncaughtException: ... 6 more
Hi @jvenborg your crash is actually unrelated. But that crash in particular should be fixed in 7.4.2
Hi @clark-signal. My apologies - but thank you very much! That sounds splendid - that crash is annoying indeed. Impossible to do anything, and woulder rather not reinstall if avoidable, which it seems to be with the update.
Any chance that this can be fixed? It's 6 mo now, issue is still ongoing
I had the same Issue today after linking a new linux desktop client to my phone and then immediately locking the app while the desktop client was still syncing contacts, etc. Linking the device succeeded somehow, but since then the android app kept crashing immediately after opening it.
I tried all of the things below, but none of those helped:
- I cleared all app data & cache, then signed into the same account again using the same phone number and existing pin.
- Putting my sim card in an old phone, signing in on that phone with the existing pin also didn't help and the app started crashing there too.
I then created a new pin and everything is working again since then which makes me think that the cloud storage for my account got corrupted somehow.
Unfortunately, I don't have access to the debug logs anymore.
I had the same issue today after linking a new linux desktop client to my phone and then immediately locking the app while the desktop client was still syncing contacts, etc. Linking the device succeeded somehow, but since then the android app kept crashing immediately after opening it.
The same happened to me today after linking a new macOS desktop client to my Samsung android 15 phone. Clearing cache or flight modus did not help. I am reluctant to clear data and reinstall, losing all chats.
pixel 8, android 14, opens for around 0.5 seconds before crashing. this happened starting this morning. in airplane mode i can get about this far:
(attached) signal-log-1719012465908.zip
factory resetting the phone and starting from scratch didn't help.
Clearing cache or flight modus did not help. I am reluctant to clear data and reinstall, losing all chats.
sorry, correction: disconnected from the internet it works normal. and I run android 14.
Chiming in, same thing happened to me just yesterday. Re-installed two Linux laptops, re-linked them and now this morning i noticed the Android app 'crashes'.
I say 'crashes', because the behaviour does not feel like a 'crash': i still get message notifications for chats when i open Signal, they keep showing in the notifications and the short time the app shows, i can see the new messages in the chat overview.
Then if i open one of the notifications, i get to that chat screen, see that chat content, but then get 'backed' out of the chat to the chats overview screen, and then get 'backed' out of the app all together. It feels like something is constantly pushing the 'back' button with about a second delay, if you can imagine.
I am currently not set up to do adb dumps, but this all seems very related to linking Signal Desktop and perhaps closing that app too quickly after having linked or something?
The linked Signal Desktop(s) work flawlessly with the account. Messages sent from there seem to come in on the Android client too.
The fact that i get backed out, screen by screen, reproducible, instead of the app crashing is kinda suss.
EDIT: Going offline/airplane mode, the Android app just works fine. Then, when i re-connect wifi, the same behaviour is seen: getting backed out from the debug log or a chat.
Hope this helps.
Perhaps relevant: one of the reinstalled laptops i gave a new name during linking and if i recall stuff just worked after that. The other laptop i reinstalled later that night and gave it the same name as the old session (which i removed before hand in the android app). Perhaps doing this in quick succession triggers it?
Re-installed two Linux laptops, re-linked them and now this morning i noticed the Android app 'crashes'.
Almost the same problem I have. I linked Signal on a Linux device. There was an existing link on a macOS device. Suddenly the Signal Android app crashed. In airplane mode the Android app doesn't crash. As soon as I disable airplane mode the app crashes again - no matter if it is already running or if I start it
Great. I f!!ed around too much. And if you f!! around you'll find out... Now i'm locked out of my Signal account. Great success. :+1: :+1:
Anyways, reinstalling and restoring from backup yielded the same crash-results.
Then i trashed everything and did not restore a backup, but aparently too many login attempts or whatever, and the pin code i had to confirm every f**ing month suddenly isnt correct anymore and now i am locked out entirely.
So be warned peeps.
If your linked desktop client still works, use that while we hope this six month old issue gets some attention.
Same problem here: tried to connect a linux device yesterday => Signal has been crashing ever since. Completely unusable now. I have tried multiple uninstalls and reinstalls - nothing changed. In flight-mode it works
Some error messages from logcat while connecting the phone to a PC via ADB
2024-06-22 16:25:57.387 10745-10809 JobRunner org.thoughtcrime.securesms W [JOB::ee0f5da9-61d2-4b18-b8f5-502bdda3bc2b][LinkedDeviceInactiveCheckJob][4] Failing due to an unexpected exception. (Time Since Submission: 342 ms, Lifespan: 2592000000 ms, Run Attempt: 1/Unlimited, Queue: LinkedDeviceInactiveCheckJob)
java.util.NoSuchElementException
at org.thoughtcrime.securesms.jobs.LinkedDeviceInactiveCheckJob.run(LinkedDeviceInactiveCheckJob.kt:2311)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:86)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:49)
2024-06-22 16:25:57.430 1381-1503 libprocessgroup system_server W SetCgroup::ExecuteForProcess: failed to open /dev/cpuctl/foreground-boost/cgroup.procs: No such file or directory
and probably this one is the more problematic one
2024-06-22 16:25:58.241 10745-10806 AndroidRuntime org.thoughtcrime.securesms E FATAL EXCEPTION: signal-JobRunner-2
Process: org.thoughtcrime.securesms, PID: 10745
java.lang.AssertionError: Must have a storage key!
at org.thoughtcrime.securesms.storage.StorageSyncModels.localToRemoteRecord(StorageSyncModels.java:51)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.lambda$getMatching$0(GroupV2RecordProcessor.java:60)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.$r8$lambda$l2yNsjTahNRscgMBxviGyETokOQ(GroupV2RecordProcessor.java:0)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor$$ExternalSyntheticLambda0.apply(R8$$SyntheticClass:0)
at j$.util.Optional.map(SourceFile:0)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.getMatching(GroupV2RecordProcessor.java:54)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.getMatching(GroupV2RecordProcessor.java:22)
at org.thoughtcrime.securesms.storage.DefaultStorageRecordProcessor.process(DefaultStorageRecordProcessor.java:51)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.process(GroupV2RecordProcessor.java:22)
at org.thoughtcrime.securesms.jobs.StorageSyncJob.processKnownRecords(StorageSyncJob.java:412)
at org.thoughtcrime.securesms.jobs.StorageSyncJob.performSync(StorageSyncJob.java:293)
at org.thoughtcrime.securesms.jobs.StorageSyncJob.onRun(StorageSyncJob.java:194)
at org.thoughtcrime.securesms.jobs.BaseJob.run(BaseJob.java:31)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:86)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:49)
2024-06-22 16:25:58.242 10745-10806 SignalUncaughtException org.thoughtcrime.securesms E java.lang.AssertionError: Must have a storage key!
at org.thoughtcrime.securesms.storage.StorageSyncModels.localToRemoteRecord(StorageSyncModels.java:51)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.lambda$getMatching$0(GroupV2RecordProcessor.java:60)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.$r8$lambda$l2yNsjTahNRscgMBxviGyETokOQ(GroupV2RecordProcessor.java:0)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor$$ExternalSyntheticLambda0.apply(R8$$SyntheticClass:0)
at j$.util.Optional.map(SourceFile:0)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.getMatching(GroupV2RecordProcessor.java:54)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.getMatching(GroupV2RecordProcessor.java:22)
at org.thoughtcrime.securesms.storage.DefaultStorageRecordProcessor.process(DefaultStorageRecordProcessor.java:51)
at org.thoughtcrime.securesms.storage.GroupV2RecordProcessor.process(GroupV2RecordProcessor.java:22)
at org.thoughtcrime.securesms.jobs.StorageSyncJob.processKnownRecords(StorageSyncJob.java:412)
at org.thoughtcrime.securesms.jobs.StorageSyncJob.performSync(StorageSyncJob.java:293)
at org.thoughtcrime.securesms.jobs.StorageSyncJob.onRun(StorageSyncJob.java:194)
at org.thoughtcrime.securesms.jobs.BaseJob.run(BaseJob.java:31)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:86)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:49)
(not feeling too great about donating to Signal every month anymore, seeing how long this ticket has been open) I am guessing, something went wrong with the pairing and now every attempt to load the list of paired devices makes the app crash => a reset-functionality would be worth its weight in gold
By the way, I tried it with a different phone-number on the same device which worked like a charm. Ofc that is useless to me but at least it proves that the problem is not the phone but is server-based and tied to the specific account.
By the way, I tried it with a different phone-number on the same device which worked like a charm. Ofc that is useless to me but at least it proves that the problem is not the phone but is server-based and tied to the specific account.
oh no. that would be a bad scene if it's what's happening for me.
I then created a new pin and everything is working again since then which makes me think that the cloud storage for my account got corrupted somehow.
That worked for me as well 🤩 I could even restore my old backups. This is exactly what I did (probably some steps are not necessary but...). Btw. I had already uninstalled and reinstalled the app a few times before that. But I assume that has no effect.
- Started Signal in Flight-Mode
- Went to Settings - Account
- Disabled the Registration Lock
- This requires an internet-connection, so while on the correct screen, I disabled flight-mode and immediately pressed the slider.
- This made the app crash but not before the setting hat been changed
- Re-started the app and went to Settings - Account - Advanced PIN settings and clicked Disable PIN
- This needs an internet-connection again but you can already click the button and then a loading-bar appears. While that is turning, disable flight-mode.
- That should then work and the app should stop crashing.
If you have never uninstalled and re-installed the app or have already re-applied your backups, this might be enough for you and you can skip the next few steps and just set a new PIN. But for me, I went a bit further to get my old chats back.
- Uninstalled and re-installed the app one last time.
- On first app-start, I selected the backup to be restored.
- After having entered my phone-number to "log-in", it asked for my PIN again.
- That was strange because I had just disabled my PIN, right???
- Well my first reaction was to just enter the old PIN again... Stupid mistake => that lead to the crash happening again.
- Therefore I had to uninstall and re-install the app again and start from scratch. => you can avoid that.
- Do not enter your old PIN here but click skip in the top-right corner.
- As a consequence, it will tell you that you will now have to authenticate by SMS-code. That is ok => do it.
- In the next step, it suggests creating a new PIN. I was a bit sick of PINs so skipped that for now.
- Now the app should start normally with all your chats restored and no crashing 🥳🥳 time to celebrate (and perhaps consume some not strictly speaking healthy beverages of your choosing).
- Now you can actually go to settings again and set a new PIN (or the old one) and it should still all work.
LESSON LEARNED: Never use Signal on Linux!
I would still REALLY appreciate a fix, though...
Dude. Totally worked.
It's funny, because for a brief second it appears as if you're going to leave all of your messages unencrypted in the cloud by removing the PIN.
My old messages are still available on my desktop, but not on my phone, so I guess that there's a local copy on the desktop.
Thanks so much for figuring this out.
On Sat, Jun 22, 2024 at 8:35 AM Florian Gubler @.***> wrote:
I then created a new pin and everything is working again since then which makes me think that the cloud storage for my account got corrupted somehow.
That worked for me as well 🤩 I could even restore my old backups. This is exactly what I did (probably some steps are not necessary but...). Btw. I had already uninstalled and reinstalled the app a few times before that. But I assume that has no effect.
- Started Signal in Flight-Mode
- Went to Settings - Account
- Disabled the Registration Lock
- This requires an internet-connection, so while on the correct screen, I disabled flight-mode and immediately pressed the slider.
- This made the app crash but not before the setting hat been changed
- Re-started the app and went to Settings - Account - Advanced PIN settings and clicked Disable PIN
- This needs an internet-connection again but you can already click the button and then a loading-bar appears. While that is turning, disable flight-mode.
- That should then work and the app should stop crashing.
If you have never uninstalled and re-installed the app or have already re-applied your backups, this might be enough for you and you can skip the next few steps and just set a new PIN. But for me, I went a bit further to get my old chats back.
- Uninstalled and re-installed the app one last time.
- On first app-start, I selected the backup to be restored.
- After having entered my phone-number to "log-in", it asked for my PIN again.
- That was strange because I had just disabled my PIN, right???
- Well my first reaction was to just enter the old PIN again... Stupid mistake => that lead to the crash happening again.
- Therefore I had to uninstall and re-install the app again and start from scratch. => you can avoid that.
- Do not enter your old PIN here but click skip in the top-right corner.
- As a consequence, it will tell you that you will now have to authenticate by SMS-code. That is ok => do it.
- In the next step, it suggests creating a new PIN. I was a bit sick of PINs so skipped that for now.
- Now the app should start normally with all your chats restored and no crashing 🥳🥳 time to celebrate (and perhaps consume some not strictly speaking healthy beverages of your choosing).
- Now you can actually go to settings again and set a new PIN (or the old one) and it should still all work.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/13255#issuecomment-2184075790, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADLR4P7LKLR5JGT7UZ6NQ4DZIWKTDAVCNFSM6AAAAAA7J42M7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUGA3TKNZZGA . You are receiving this because you commented.Message ID: @.***>
I am experiencing this issue as well after a similar situation. In my case it was a Windows client.
I'd had issues linking this machine after getting a new phone, and had uninstalled then reinstalled the desktop client. The desktop client now is linked and works, my phone can sometimes get notifications through but that's it.
Hope this gets some attention soon.
EDIT/UDPATE: Following fgubler's steps above: https://github.com/signalapp/Signal-Android/issues/13255#issuecomment-2184075790 worked to resolve the issue for me.
I had the same Issue today after linking a new linux desktop client to my phone and then immediately locking the app while the desktop client was still syncing contacts, etc. Linking the device succeeded somehow, but since then the android app kept crashing immediately after opening it.
I tried all of the things below, but none of those helped:
- I cleared all app data & cache, then signed into the same account again using the same phone number and existing pin.
- Putting my sim card in an old phone, signing in on that phone with the existing pin also didn't help and the app started crashing there too.
I then created a new pin and everything is working again since then which makes me think that the cloud storage for my account got corrupted somehow.
Unfortunately, I don't have access to the debug logs anymore.
I think your issues are completely different than the original issue.
My issue had probably nothing to do with the desktop client.
Also I cannot change the pin since it is always crashing (also in airplane mode) unfortunately.
Ok, that makes sense. I guess, I will create a separate Issue, then. Update: I created this new issue to cleanly look at this bug separately from the original one of this ticket. https://github.com/signalapp/Signal-Android/issues/13603
Maybe those who have posted here, could also add their voices to the new ticket to get more attention to it...