REPRODUCIBILITY: yes, on two devices
OS VERSION: 5.0.0.67
HARDWARE: Sony Xperia 10 III
UI LANGUAGE: English
REGRESSION:
DESCRIPTION:
Signal messenger app 7.41.3 is closing as soon as it is starting. Was working until noon. Phone updated to Tampala yesterday evening.
PRECONDITIONS:
STEPS TO REPRODUCE:
start phone
start app
app closes on startup
EXPECTED RESULT:
Signal to start and run
ACTUAL RESULT:
Signal is not starting and not accessable at all
MODIFICATIONS:
none
ADDITIONAL INFORMATION:
3 Likes
Can confirm. Last successful login around 8am CEST. Tried again around noon → crash.
XA2 on 5.0.0.67; Signal 7.40.2, last update May 2nd.
Can confirm, Xperia 10 II on 5.0.0.67, Signal 7.41.3
App is apparently running properly in the background, since tapping on an incoming message popup leads to the conversation window where you can normally send messages.
Clicking the “Back” button leads to main window disappearing.
Signal Desktop App works fine as well.
Anyone else can see the “Donate to Signal” message when trying to start?
It’s not on other pages so it might cause the crash when viewing main page.
I can access any chat by sharing image from another app and choosing the chat I want to view.
Accessing different chats via the “share from different app” works for me as well.
First I thought I saw the popup reminder for my PIN, but it could have been the “Donate to Signal” as well, they look similar.
I’m happy to provide any kinds of logs.
Xperia 10 III, SFOS 5.0.0.67, Signal 7.41.3
Background-Service is working, when I get a message, I can open Signal App by touch on notification. As long as I dont press the Back-Button, I can use Signal. If i press Back-Button Signal Gui closes. If it’s closed I cannot open it again.
I think in the 3ms, when the window opens, before it closes itself, I maybe see the ‘enter PIN’ dialog.
Opening from App-Chooser is not working.
Sounds like these:
opened 07:46AM - 21 Jun 24 UTC
closed 03:13AM - 22 Jun 24 UTC
- [x] I have searched open and closed issues for duplicates
- [x] I am submitti… ng 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 keeps on crashing, I'm not sure why...
### Steps to reproduce
- Click icon to open the app
Not sure if this helps, but the last thing I did was forward myself an image from "Note to Self" into the same "Note to Self" chat because it's on phone but not on my computer's signal app (I recently switched computers..). Overall, pretty shitty experience and now I can't seem to even use the app it just keeps on crashing - I've already tried re-installing the app and restarting my phone...
EDIT:
- Turning off mobile data/wifi seem to stop the app from crashing but it's obviously useless without data...
**Actual result:** App minimizes/closes and I proceed to go back to my home screen
**Expected result:** I should be able to open the app, navigate and message people
### Screenshots
### Device info
**Device:** Pixel 5
**Android version:** 14
**Signal version:** 7.8.1
### Link to debug log
I can't. The app is broken
EDIT:
Got the log when I turned off data/wifi
[signal-log-1718958262102.zip](https://github.com/user-attachments/files/15924989/signal-log-1718958262102.zip)
opened 02:40PM - 19 May 25 UTC
### Guidelines
- [x] I have searched searched open and closed issues for duplic… ates
- [x] I am submitting a bug report for existing functionality that does not work as intended
- [x] This isn't a feature request or a discussion topic
### Bug description
Everytime I try to open the Signal app, it crashes after I enter my pin or use biometrics to unlock the app. I have tried restarting my phone and using airplane mode, but neither work. I also don't have a backup because I just got this phone a week ago and forgot to enable backups
### Screenshots
_No reponse_
### Device
Samsung Galaxy S23 Ultra
### Android version
15
### Signal version
7.42.1
### Link to debug log
https://debuglogs.org/android/7.42.1/e8f87d613809718a85b428af8147f6b4bae06eedf5275fb6f5ff6162c3e92153
opened 02:29PM - 19 May 25 UTC
### Guidelines
- [x] I have searched searched open and closed issues for duplic… ates
- [x] I am submitting a bug report for existing functionality that does not work as intended
- [x] This isn't a feature request or a discussion topic
### Bug description
- App (from f-droid) crashes at startup on Graphene OS.
- When I attempt to open the app itself (from the launcher) it crashes.
- I tried re-opening the app after reboot. Same issue.
- When I share a photo with a contact (frm the gallery > share > Signal) it works well. I can even stay in the chat and see that the message arrived. If I tap "back" to see the list of messages, it crashes.
- When I open notifications that take me straight to a chat, it works well. I can see and send messages.
- The OS task switcher shows the attached image.
### Screenshots

### Device
Pixel 7 pro
### Android version
- Android 15
- kernel: 6.1.134
- build number 2025050700
### Signal version
7.41.3
### Debug log
```
type: crash
osVersion: google/cheetah/cheetah:15/BP1A.250505.005.B1/2025050700:user/release-keys
package: org.thoughtcrime.securesms:154200, targetSdk 34
process: org.thoughtcrime.securesms
processUptime: 2980 + 372 ms
installer: org.fdroid.fdroid
java.util.concurrent.ExecutionException: com.bumptech.glide.load.engine.GlideException: Failed to load resource
There were 3 root causes:
java.io.FileNotFoundException(null)
java.io.FileNotFoundException(null)
java.io.FileNotFoundException(null)
call GlideException#logRootCauses(String) for more detail
at com.bumptech.glide.request.RequestFutureTarget.doGet(RequestFutureTarget.java:217)
at com.bumptech.glide.request.RequestFutureTarget.get(RequestFutureTarget.java:130)
at org.thoughtcrime.securesms.megaphone.MegaphoneComponentKt$MegaphoneImage$1$1$1.invokeSuspend(MegaphoneComponent.kt:300)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:707)
at [[ ↑↑ Original Trace ↑↑ ]].(:0)
at [[ ↓↓ Exception Message ↓↓ ]].(:0)
at com.bumptech.glide.load.engine.GlideException: Failed to load resource
There were 3 root causes:
java.io.FileNotFoundException(null)
java.io.FileNotFoundException(null)
java.io.FileNotFoundException(null)
call GlideException#logRootCauses(String) for more detail.(:0)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [androidx.compose.ui.platform.MotionDurationScaleImpl@69d3206, androidx.compose.runtime.BroadcastFrameClock@cd050c7, StandaloneCoroutine{Cancelling}@e3936f4, AndroidUiDispatcher@1d2ee1d]
Caused by: com.bumptech.glide.load.engine.GlideException: Failed to load resource
There were 3 root causes:
java.io.FileNotFoundException(null)
java.io.FileNotFoundException(null)
java.io.FileNotFoundException(null)
call GlideException#logRootCauses(String) for more detail
```
Anyone able to access via Airplane mode?
3 Likes
Anyone able to access via Airplane mode?
Does not work for me (x10iii - AppSupport 11 - API30) :frowning
This morning the app works. This afternoon Signal crashes !
Between the morning and the afternoon : no update of anything !
A problem from Signal ? On my desktop, Signal works. And i was able to make a call with Signal Desktop to my son with Signal that is on Android.
Same problem on the XA2 of my wife !
FYI: successfully tried this workaround:
opened 02:40PM - 19 May 25 UTC
closed 05:25PM - 19 May 25 UTC
**FIX FOUND!**
- Set clock back to 9 hours ago
- Opened Signal, it worked
- Mad… e a local backup so I would have my messages
- Reinstalled Signal
- Restore from backup
- Set back my clock to current time
Now it works again!
Keeping the original issue down here for continuity's sake. Thank you to @JustToby22 for the fix!
### Guidelines
- [x] I have searched searched open and closed issues for duplicates
- [x] I am submitting a bug report for existing functionality that does not work as intended
- [x] This isn't a feature request or a discussion topic
### Bug description
Everytime I try to open the Signal app, it crashes after I enter my pin or use biometrics to unlock the app. I have tried restarting my phone and using airplane mode, but neither work. I also don't have a backup because I just got this phone a week ago and forgot to enable backups
### Screenshots
_No reponse_
### Device
Samsung Galaxy S23 Ultra
### Android version
15
### Signal version
7.42.1
### Link to debug log
https://debuglogs.org/android/7.42.1/e8f87d613809718a85b428af8147f6b4bae06eedf5275fb6f5ff6162c3e92153
and was able to read pending messages and reply.
However, once I set the phone back to the current time, Signal kept crashing again.
I can confirm this bug.
Signal 7.41.3,
Android AppSupport 11, API level 30,
SFOS 5.0.0.67,
Xperia 10 II
VERY MAD!
The workaround is working. On my phone, it is not 9 hours. It is exactly 15:00, every time before 15:00 Signal is working, at 15:00 and after, it crashes.
Yes, on Xperia 10 iii signal works “in the morning” (i.e. when the clock is set back before 15:00) and afterwards it crashes. Interesting indeed. It has nothing to do with automatic clock time sync. I can toggle the behaviour just by switching between time.
I tried the workaround. I deviated in one point. I set the time back to the current time before the reinstall. Now it is working. I hope it will stay like this.
So did the donation banner appear today, maybe around 15h00?
Might be a reason for the crash?
Louis
19 May 2025 19:03
15
For me (on Xperia 10 iii) launching the app in landscape mode worked as a workaround.
If I’m inside a conversation I can use the app in portrait as long as I don’t go back to the conversation overview because then the app will crash.
2 Likes
rope
19 May 2025 19:17
16
I see the exact same problem
starting the App in landscape mode works here as well.
I had the same problem on C2 and XA2, but installing the latest version (7.41.4) seems to have solved it.
4 Likes
7.41.4 fixed it for me, too
Yes, Signal version 7.14.4 fixed the issue for me:
2 Likes
Xperia 10 III, SFOS 5.0.0.67, still on Signal 7.41.3
Crashed on start up this afternoon. Reinstalled and restored from backup. Everything works again.
Updated to 7.41.4 now.
1 Like