-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Electron] Hangs at "loading", TypeError: conversation.save(...) is not a function #1970
Comments
Additional info: After letting it hang for a while I'm noticing the unread message count in the window title slowly (VERY slowly) counting up. Possibly it's not completely stuck, just very very slow. The above error message does look like something is wrong, though. |
Please send a log whenever makes sense. The log entries surrounding that error you included will be instructive in tracking down the core issue. |
Ah, I just figured out what it is. This pull request recently made us more resilient to phone numbers we believe are invalid: #1968 But now we have errors in other scenarios, as you've seen. It looks like you got a message from someone with an invalid phone number, so |
Hmm. Any idea how to find out whose message it might be that causes the error? To me, all my contacts have valid numbers and since Signal Desktop won't start properly I can't see on which of the thousands of messages in my history it is choking. At least not from stdout. Is there another log file? Sorry if I'm somehow too blind to find it.
Am 16. Januar 2018 18:57:10 MEZ schrieb Scott Nonnenberg <[email protected]>:
…Ah, I just figured out what it is. This pull request recently made us
more resilient to phone numbers we believe are invalid:
#1968
But now we have errors in other scenarios, as you've seen. It looks
like you got a message from someone with an invalid phone number, so
`conversation.save()` didn't return a Deferred. Please reach out to
support, or to me directly, with that number and we can fix our phone
number parsing.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#1970 (comment)
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
|
In the log lines right above that error, you should see the last three digits of the problematic phone number, and that should help you track it down. |
I sent you an e-mail with the uncensored log and possibly offending phone numbers. |
My Signal for Windows got also stuck. |
@peterpanondrugs You can find my email addresses on my github profile. But do know that we redact sensitive information like group and phone numbers from that log, so it should be safe to upload. Lastly, please enter a new bug, following the full issue template. Thanks! |
has it any relation to this #2196 ?! I posted my txt file there. |
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. |
This issue has been closed due to inactivity. |
Bug description
Since I pulled the latest version from this repository, the application hangs on startup at the "loading" screen. I'm starting it from command line with
npm start --production=true
. The last stdout entry is as follows:Steps to reproduce
npm start --production=true
Platform info
Signal version:
pulled from git today
Operating System:
Linux 4.12.12-gentoo #1 SMP PREEMPT Sat Nov 25 19:22:19 CET 2017 x86_64 Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GenuineIntel GNU/Linux
Linked device version:
OnePlus One - LineageOS 14.1 (Android 7.1.2)
The text was updated successfully, but these errors were encountered: