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

Cannot send from Desktop App after Upgrade to v1.18.0 #2914

Closed
azulskyknight opened this issue Nov 17, 2018 · 8 comments
Closed

Cannot send from Desktop App after Upgrade to v1.18.0 #2914

azulskyknight opened this issue Nov 17, 2018 · 8 comments

Comments

@azulskyknight
Copy link

azulskyknight commented Nov 17, 2018

Send Failed, on desktop app. More info on each message reports : Rate limit exceeded, please try again later. (original: promiseAjax: invalid response; code: 413) Not sure how to troubleshoot further.

I've got 1 contact I use Signal with, and I hardly think the traffic we generate should impact any sort of rate limit.

I've removed the app and reinstalled it. I've cleared its data and relinked it to my phone. I've cleared my phone app's data, reconfigured it, and deleted data on the desktop app and relinked it yet again.

Phone app works perfectly, desktop app can receive messages but not send.

Issue presented immediately after app restart upgrading from previous release. I'm unable to locate a download for v1.17.0 to verify if reverting to the previous version clears the issue.

Windows 10 Professional 1803, running Signal Desktop APP version 1.18.0
Phone is running Android 7.0, Signal APP version 4.29.7

Please advise on how to investigate further.

Debug Log: https://debuglogs.org/d6db90af7a9200a86cb9281ad900e86eab5d464e5af0c432ef0fd92e0820c2c7

@bxkx
Copy link

bxkx commented Nov 18, 2018

I'm having the same problem, #2913
I downgraded to 1.17.3 and I can now send messages again to the contact I couldn't with 1.18.0

@KolyaKorruptis
Copy link

Same problem since 1.18.0 on multiple machines.

@rfc805
Copy link

rfc805 commented Nov 19, 2018

Seems there are no older versions in the repository either, anyone know where to find an 'official' older release? Rather odd that this can be released to the main branch with nobody noticing, and nobody noticing this issue report either?

@azulskyknight
Copy link
Author

azulskyknight commented Nov 19, 2018

According to the logs, this appears to be a duplicate of 2913.

I've also noticed in those same logs my username is being leaked in the profile path, some of the log entries are redacting this information, some are not.

I have not downgraded by version of Signal due to no apparently official older versions being available. Certainly it's out there on the Internet, but I don't make it a habit of installing things from unofficial sources.

@bxkx
Copy link

bxkx commented Nov 19, 2018

On Windows, Signal seems to save a lot of old installers in ~/AppData/Roaming/Signal
By changing the official download link from 1.18.0 to e.g. https://updates.signal.org/desktop/signal-desktop-win-1.17.0.exe lets you download the older version just fine.

@azulskyknight
Copy link
Author

Derp... yes that's true, so https://updates.signal.org/desktop/signal-desktop-win-1.17.3.exe and oh look there's the last version that worked!

Also, nice to know about the app data piling up old versions, but sadly I nuked mine during reinstall trying to isolate the issue.

@azulskyknight
Copy link
Author

Ok so to be clear, installing 1.17.3 from the above link, and relinking the desktop client to my phone results in things working as intended.

1.17.3 working debug log: https://debuglogs.org/f15b4520233d5718686f0e0be5d011972d26191b7b22670f0a87ae8515bcae0e

Then, apon closing the app or allowing it to update, it automatically updates to 1.18.0, and we're back to broken again.

https://debuglogs.org/fb0e0bdd54144e6f534395e303312fc8c49ec8423c940b552e9740fdf817d59b

@scottnonnenberg-signal
Copy link
Contributor

Closing as a duplicate of #2913

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants