Skip to content
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

Closed
1 task done
chaoscommander opened this issue Jan 13, 2018 · 11 comments
Closed
1 task done

Comments

@chaoscommander
Copy link

chaoscommander commented Jan 13, 2018

  • I have searched open and closed issues for duplicates

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:

`{"name":"log","hostname":"redacted","pid":18031,"level":50,"msg":"Top-level unhandled error: TypeError: conversation.save(...).then is not a function
at file:///home/redacted/Programme/Signal-Desktop/js/models/messages.js:532:45`

at file:///home/redacted/Programme/Signal-Desktop/js/components.js:3230:33

at fire (file:///home/redacted/Programme/Signal-Desktop/js/components.js:3073:30)

at Object.fireWith [as resolveWith] (file:///home/redacted/Programme/Signal-Desktop/js/components.js:3185:7)

at deferred.(anonymous function) (file:///home/redacted/Programme/Signal-Desktop/js/components.js:3275:34)

at Object.options.success (file:///home/redacted/Programme/Signal-Desktop/js/components.js:22009:13)

at IDBTransaction.writeTransaction.oncomplete (file:///home/redacted/Programme/Signal-Desktop/js/components.js:21617:25)","time":"2018-01-13T17:01:08.828Z","v":0}`

Steps to reproduce

  1. Install from git using bower and npm
  2. Start from command line with 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)

@chaoscommander
Copy link
Author

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.

@scottnonnenberg
Copy link
Contributor

Please send a log whenever makes sense. The log entries surrounding that error you included will be instructive in tracking down the core issue.

@scottnonnenberg
Copy link
Contributor

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.

@chaoscommander
Copy link
Author

chaoscommander commented Jan 16, 2018 via email

@scottnonnenberg
Copy link
Contributor

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.

@chaoscommander
Copy link
Author

I sent you an e-mail with the uncensored log and possibly offending phone numbers.

@peterpanondrugs
Copy link

My Signal for Windows got also stuck.
Is it safe to upload the log files without releasing personal information?
Let me know, then i will upload here the *.txt otherwise i need an email adres.
Thx

@scottnonnenberg-signal
Copy link
Contributor

@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!

@peterpanondrugs
Copy link

has it any relation to this #2196 ?! I posted my txt file there.
happy easter! :)

@stale
Copy link

stale bot commented Sep 29, 2021

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 stale bot added the stale label Sep 29, 2021
@stale
Copy link

stale bot commented Oct 6, 2021

This issue has been closed due to inactivity.

@stale stale bot closed this as completed Oct 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants