Startup crash #6838
Comments
|
same here. Sent the error report. |
|
same here.... with no error. App closed. |
|
This is the stack trace |
|
Moto G4 with Nougat 7.0 here, I'm signing up on this crash. Can't post a log because well, I can't get that far into the app before it crashes |
|
Updated to latest beta 4.9 from Play Store and now Signal crashes for me too. The app shows'updating database and then crashes at startup |
|
Same problem with a Pixel on Android 7.1.2 with security patches from july. I've also sent a bug report. |
|
4.9.0 crashes on my OPO3 with 7.1.1 on startup too. Tried to clear the app cache but this didn't work. |
|
Same problem in android marshmallow. Can't downgrade without uninstalling. |
|
Is this an issue that affects mostly German users? Or are there just more German beta users? |
|
The Americans are probably mostly still asleep. Those who wake up early and read this may want to wait for 4.9.1. |
|
@franziskuskiefer Thanks for the stack trace. Can anyone who's seeing this with the ability to capture ADB update to this debug APK: ...and post the log here? It will still crash, but should include more information to help me understand what is failing to fix it. |
|
Upgraded to 4.9.0 today and it worked fine until I received an SMS. Now it crashes on start without any errors. |
|
@kpuljek Please post a debug log here for us to be able to determine the source of the crash. |
|
@moxie0 not sure what's supposed to be in the debug log. But this is what I get when running the APK you provided. (I replaced the phone numbers with ******.) It looks like it's crashing while migrating the SMS/phone numbers. |
|
Hey! I ran adb logcat and used the .apk you provided and tried running it 5 times (all five crashed) and piped it into a txt file. I hope this can be of help. If I did it wrong, just let me know and I'll do it again. :) If there is any private information in the log (I couldn't find any, but it's huge), download it and please delete the post/attachment. |
|
Thanks @franziskuskiefer, would you be comfortable emailing me (moxie+github@whispersystems.org) the full unredacted log? It's something to do with the numbers, so I'd need to see them in order to figure out why it's failing. |
|
@kpuljek Thanks, that's helpful. Looks like you're experiencing something different from the other folks here, I've created another build with additional logging in the area where your crash is occurring: If you could get me the logcat output from that, it should help clarify what's going on with your crash. This log might include phone numbers, so feel free to email it to me if you'd prefer (moxie+github@whispersystems.org). Thanks! |
|
Upraded, redid the logcat and I don't see any numbers in the log, so I'll post it here. I hope this helps, it looks the same as the first to me. |
|
@kpuljek Thanks! Hah the problem is that there isn't a number in there =) Here's another one with more debugging: |
|
Still no numbers |
|
OK, I was a bad guy and used TitatniumBackup this morning to backup before updating to 4.9.0. Anyway, found these two entries: I'm pretty sure I have no pending expiring messages. Maybe from some old old beta?! |
|
Don't want to mess around in this bug but I am unsure if its related or should be a standalone issue. |
|
@mr-gosh Well, if anything we have the same device. Maybe there's something to that |
|
@McLoo I'm Swedish and I have this exact issue, so if it turns out there's a reason Americans aren't affected I'd say it's because of the letters we Europeans use that you guys don't. |
|
I'm in the US and having the maybe same problem. Everything was working until the beta update. This morning, I uninstalled and reinstall Signal and it opened and worked fine. I then linked it to my desktop and now signal crashes on open and the desktop app is working. EDIT: This is #6840 |
|
@ruicruzpt this could easily be my problem, too, considering it started crashing after I received an SMS from my mobile provider. |
|
Same issue too. dreamlte (Galaxy S8) |
|
@moxie0 I guess many people store phone numbers in their phone's address book without the international prefix (I don't - but many do). |
|
🤔 I'm confused. Just changed a valid number in android contact app from valid +491234567890 to +4901234567890 and sending messages worked well 😕 |
|
@RiseT Thanks, I think this is why non-Americans are mostly affected. This change should eliminate this kind of confusion in the future, but it's tripping up the migration. The bad news is that I think I have to somewhat arbitrarily delete "recipient preferences" in cases like this where a conflict emerges. |
|
@p4nci I've tried to call myself using "+4901234567890" and I got a message that the number wasn't allocated, i. e. it didn't work. The official format when using an international prefix is definitely without that "0", but perhaps some providers filter that "0" in order to fix the faulty number and make it work. |
|
@RiseT I did not tried calling but sending signal messages and that worked well EDIT: just tested aslo with a signal call: had no problems and as expected a "normal" call it's not possible |
|
@p4nci Ah, Signal message, ok. I guess the reason is another odd thing I've noticed some time ago: The phone number of an existing Signal contact doesn't change in Signal if you change that contact's phone number in Android's address book. I've just tried this and appended a "1" to the phone number of an existing Signal contact in Android's address book. Even after refreshing, that appended "1" didn't show up in Signal. I would expect that contact getting listed as "non-Signal", as with the appended "1" it's a new phone number that's not registered with Signal's server. |
|
@RiseT well in my case signal "updated" a number from +49123... to +490123... |
|
Still crashing on version 4.9.1 |
|
4.9.2 works |
|
Also 4.9.2 does not work. annoying. |
|
4.9.2 does not work here. |
|
It looks like 4.9.2 is touching the right code but isn't fully resolving the issue (or my database is completely broken now). The trace looks pretty much the same except for the last line. It can't find the |
|
4.9.2 still crashes on my phone, so it seems there are several issues concerning crashes on startup. |
|
4.9.2 crashes for me as well, this time there's a new SQL exception (looks like a typo in table name?): |
|
@grendello could you file a new issue for this? |
|
I can confirm that 4.9.2 also crashes always. I sent the log via Google Play since I've currently no way to get a catlog manually. |
|
Both 4.9.1 and 4.9.2 fixed my issue, just to report! |
|
4.9.2 still crashes for me, but at a different point at 4.9.0. The latter crashed immediately when the app window opened, now after updating to 4.9.2 it crashes a second later: after it already shows the "enter passphrase" dialog. |
|
Version 4.9.3 is okay now! Yeah! |
|
Can confirm, 4.9.3 works for me too! |
|
4.9.3 fixes the issue for me. |
|
Confirmed that 4.9.3 fixes the crash for me as well, yay! :) |
|
@bgoerner Thank you for being a beta tester, if you would like a less "annoying" life of peace and tranquility, consider running the production releases instead. |
I have:
Bug description
Signal for Android crashes on startup-.
Steps to reproduce
Actual result: Signal for Android crashes
Expected result: Signal for Android should open
Screenshots
Device info
Device: Huawei Nexus 6P
Android version: 7.1.2
Signal version: 4.9.0
Link to debug log
No adb handy right now, but log is in the screenshot above. Signal debug info isn't available because it's a startup crash.
The text was updated successfully, but these errors were encountered: