Signal-Desktop
Signal-Desktop copied to clipboard
signalapp
Verification Failed, Please Retry Later
Using a supported version?
- [X] I have searched searched open and closed issues for duplicates.
- [X] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.
Overall summary
Ubuntu 22.04 Signal 6.46.0
I'm reporting extensive bugs in the capcha system, but things are not getting better. To the contrary. Recent, previous bug reports 1, 2, 3 - I believe related, 4 - on iphone.
As you see with [1], I was having trouble getting Signal to respond properly once I completed a capcha. I was able to get around that by restarting, sometimes more than once. Now, I am filing out a capcha, on each return to Signal I"m getting the message, "Verification failed, Please retry later." Then I restart, and try again, with the same message. I've done that now five times, so at this point I'm completely stuck. None of this had anything to do with the groups that have been causing me grief in the past, forcing multiple capchas on me in a row. I had just forwarded a message to 2 groups from a 3rd, all of which have behaved well in the past.
I produced this log.
Edit: I did two capchas in a row, without a restart in between. The second time I returned to signal, it was silent, no message, but the "Verify to continue messaging" window didn't go away.
New log.
Steps to reproduce
Above
Expected result
Above
Actual result
Above
Screenshots
No response
Signal version
6.46.0
Operating system
Ubuntu 22.04
Version of Signal on your phone
6.59.0.23
Link to debug log
No response
The version is now 6.47.0.
I got 5 capchas in a row on startup. No complaints about verification failing, just repeated capcha. Log.
I'm still sometimes getting "verification failed" even on restart of Signal. Here's a log regarding that Log.
Repeated shutdown/ restart, with long waits, not helping to clear that the "verification failed" message every time I complete a capcha. I've lost count, but I've done maybe 6 or 7 of them. I now have a message to a group on hold, with the spinner going.
Message that is failing to be sent:
SentToday 8:23 PM (1707884604822)
That message is listed as "pending" for all members of the group. From my experience with something like this perhaps a year ago, I think it may be 24 hours before that times out.
Now version 6.47.1
So I'm getting completely locked out now and blocked from posting on a couple of groups. This is a log subsequent to many solved capchas and multiple restarts over two days. Log.
Also, @jamiebuilds-signal had told me that if I blocked 6 people, that should help with (at least) the problem reported in [2] (see the OP, above). I have blocked those, to no effect, at least on this bug:
!serviceIdEndsWith:f47 No results
:fab I've communicated with this person. They are not in any of my groups.
:7e8 I've communicated with this person. They are in the small grup that often asks for 2 capchas in a row.
:10f I've never communicated with this person. They are on a group that I'm admin for. I have never communicated with them directly, but I have through the group.
:45e Two results. One is not on signal any longer (though I've communicated with them in the past) The other is on Signal, I have communicated with them in the past, they are on a group for which I am admin and one other. Neither group has been problematic
:a15 I've never communicated with this person. This person is on the very large group that is problematic
I can't get any verifications to go through, and I'm getting locked out of more groups. Log.
A few minutes later, after a couple of more capchas, another log
Reboot, followed by 5 completed capchas. No feedback from Signal save for the first capcha, for which I got the "Verification Failed, Please Retry Later." Then I gave up. Log
I've got 3 groups now where messages are not just sitting with a spinner, but are completely failing.
I'm getting messages failing silently. Signal really needs to be more noisy when, in a long thread, a message times out and doesn't end up being sent.
Here is the log relevant to the details below:
Here is a message from two days ago that was partially sent with one person for whom, after some great length of time, it failed. I've tried sending it again, and that person has now returned to "pending". They will stay there for some time, and then the message will probably fail again (?) There are also many people for whom I'm told that message was "sent to", though not "delivered to" (as with the bulk of them):
SentFeb 15, 2024, 3:39 PM - (1708040375046)
A later message on that same group, that is showing two check marks, shows a number of people for whom it was "sent to" but not "delivered to". Oddly, that one person who failed the previous message is appearing in the "sent to" list differently from the others, though there is some icon missing so I can't interpret what might be going on here (notice the gap):
SentToday 3:58 PM - (1708214295355)
I don't know if any of this has to do with that specific person, but they are in four of my groups. In a second one, I'm getting a "Send Failed" on a message that was "Not sent" to anyone on the group (ie. everyone is listed as "not sent"):
SentYesterday 6:14 PM - (1708136048906)
An earlier one on that same group is getting a "Not Sent" for just that one person:
SentFeb 15, 2024, 7:45 AM - (1708011957880)
On the other hand, a third group that they are in has a message that was successfully sent (two check marks, though there are many "Sent to" as opposed to "Delivered to"). There, this specific person is in the "Sent to" group, but again with this odd difference in the listing:
SentToday 4:38 PM - (1708216738621)
Edit: Regarding that last message, there are still many in the "Sent to" column, but that one person has migrated to "Delivered to", though still with this odd difference - note, no time is listed!:
Now this is the group that was giving me so much grief in my report [2] (see the OP). I sent a message two days ago, and it came up as "Send failed" with everyone is listed as "Pending" (see the spinner in the image, still going) except one person, for which it was "Not Sent." Thing is, that person had left the group, so I'm not sure why they are still listed there at all:
SentFeb 15, 2024, 3:49 PM - (1708040963719)
Edit: I tried deleting that message and resending (new log). It's 5 minutes now, and everyone is listed as Pending. There seems to be no action at all:
SentToday 7:37 PM - (1708227440002)
I wonder how much is due to the capcha issue, because on shutdown and restart, I'm back to the request for capcha that is responded to with "Verification failed, please retry later." I'm dead in the water. I can't get through a /single/ capcha.
Edit: I deleted all these and resent from my phone, where capchas worked and were not excessive.
Until yesterday, I did all posts on 4 problematic lists through my phone (desktop -> note to self -> forward to the list from phone). Yesterday and today I sent to one of those lists directly from the laptop, got one capcha, and was able to get through it unscathed.
Alright, I just edited that message, it wanted another capcha, and then it fails. Log
Reboot of the machine didn't help. Log.
As far as I can tell, this problem appears to be fixed. (Version 7.0.0). Not sure if I should close, so I'll leave it open.
Edit: Belay that - no, problem is still here. Log
I posted this as a new bug.
We are now at version 7.3.0. The problem remains, plus a new problem. At the very moment I try to submit the debug log, I get the following, plus a request that I complete another capcha. The debug log, when I try to attach here, says "File size too big: 25MG are allowed, 186MB were attempted to upload." Maybe you can give me a place to upload it?
This is still a problem, and in this case, I got capchas when posting to a group that /I created/! Now I can't post any more. Log.
I just started getting this today right after creating a group and adding about 20 people to it (all of whom are friends). On the desktop app.
Ya, it's beginning to spread. I've had trouble for months, but other people are starting to report the issue on the my threads.