Signal Beta: Captcha verification says it succeeds, but I'm prompted to redo captcha verification.

[Geremia]

Using a supported version?

• I have searched searched open and closed issues for duplicates.
• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

Captcha verification says it succeeds, but I'm prompted to redo captcha verification. This continues in a loop (similar to some other issues , like #5821).

Steps to reproduce

1. Open Signal Desktop Beta
2. Click "Continue" to captcha verification.
3. Solve the captcha in browser.
4. Open the link back in Signal Beta.
5. It says verification successful, but it prompts to do captcha verification again.

Expected result

That it not prompt me again to do catpcha verification.

Actual result

It goes into a loop of prompting me.

Screenshots

Signal version

7.0.0-beta.2

Operating system

Linux

Version of Signal on your phone

No response

Link to debug log

https://debuglogs.org/desktop/7.0.0-beta.2/a86320bc4a52f6477175c9284587ee24bc9bbb87b582058451b8dc63b2338e2e.gz

Relevant part after going through a few iterations of the re-captcha loop:

{"level":30,"time":"2024-02-26T20:26:45.760Z","msg":"handleSignalRoute: Matched signal route: captcha"}
{"level":30,"time":"2024-02-26T20:26:45.761Z","msg":"challengeMain.handleCaptcha: sending captcha response to 1 handlers"}
{"level":30,"time":"2024-02-26T20:26:45.762Z","msg":"challengeMain.onRequest(conversationJobQueue.run(PNI:[REDACTED]bf2 ([REDACTED]5ba), NormalMessage, 1708973197744)): got response after 236838ms"}
{"level":30,"time":"2024-02-26T20:26:46.405Z","msg":"challengeMain.onRequest(conversationJobQueue.run(PNI:[REDACTED]bf2 ([REDACTED]5ba), NormalMessage, 1708973197744)): received challenge request, waiting for response"}
{"level":30,"time":"2024-02-26T20:27:32.254Z","msg":"handleSignalRoute: Matched signal route: captcha"}
{"level":30,"time":"2024-02-26T20:27:32.255Z","msg":"challengeMain.handleCaptcha: sending captcha response to 1 handlers"}
{"level":30,"time":"2024-02-26T20:27:32.256Z","msg":"challengeMain.onRequest(conversationJobQueue.run(PNI:[REDACTED]bf2 ([REDACTED]5ba), NormalMessage, 1708973197744)): got response after 45851ms"}
{"level":30,"time":"2024-02-26T20:27:32.751Z","msg":"challengeMain.onRequest(conversationJobQueue.run(PNI:[REDACTED]bf2 ([REDACTED]5ba), NormalMessage, 1708973197744)): received challenge request, waiting for response"}

[Geremia]

@cuu508 here said:

Submitting a CAPTCHA solution to Signal does not affect the send attempts that already failed. It increases the chances that future sends will succeed.

Is this why I'm getting this issue here? I was trying to resend a message that failed, but in non-beta Signal Desktop, I am able to send the message to the recipient, so the captcha verification did work, despite Beta re-prompting me.

[tuxpizza]

I am having the exact same issue on Desktop stable 7.0
Did not have this on 6.47.
I am currently am unable to use Signal desktop.

[trevor-signal]

@tuxpizza sorry about that; can you share a debuglog?

[myf]

pure empirical evidence: I also encountered this: captcha succeeded but signal desktop still wants me to verify. This happened when I was on vpn. When I took the vpn off the verification process went through.

Here's circular logic: using VPNs would sometimes trigger captcha verification, and if what i thought was true this verification cannot go through while on vpn...

[studiok87]

@tuxpizza sorry about that; can you share a debuglog?

Same problem here, Linux Mint and Firefox. Tried to submit a debug log, but I get a popup
"Something went wrong with the upload! Please email support..."
Will send it now via email.

[jasonribble]

This is making Signal nearly unusable on my phone and Desktop.

Funny thing is too, is that I can skip verification and still send messages. So it doesn't even seem that the spam filtering even works.

[scottnonnenberg-signal]

@jasonribble Hey there - I'm sorry these captchas are happening to you. If you send a debug log from each of your devices (primary phone, and all linked devices) we can try to track down what's happening. Thanks!

[jasonribble]

How do you recommend I send them to y'all?

[scottnonnenberg-signal]

@jasonribble Usually you will upload the debug log in each of your Signal clients, then paste the resultant URLs here. But you can also send the set of URLs to [email protected], referencing this issue.

[AJolly]

I'm also having the problem that signal beta triggers the captcha, but then it wants to open the signal non-beta app.

(And even in the normal app, it keeps asking me to reverify).

I'd send a debug log, but both versions are just hanging on the log page, possibly because my log files are too big.

Also this got triggered when sending a message to an existing contact, so its pretty weird to me that I'd run into this issue.

[jamiebuilds-signal]

@AJolly Can you follow the steps on https://support.signal.org/hc/en-us/articles/360007318591-Debug-Logs-and-Crash-Reports#:~:text=Steps%20to%20share%20a%20debug%20log%20if%20Signal%20Desktop%20does%20not%20open under the Desktop > "Steps to share a debug log if Signal Desktop does not open" section?

[AJolly]

I've got both log files from when the event happened, but they're 200 Mb each. For what it's worth I was able to fix the issue by temporarily switching my default browser.

…

On Wed, Jul 10, 2024, 3:54 PM Jamie Kyle ***@***.***> wrote: @AJolly <https://github.com/AJolly> Can you follow the steps on https://support.signal.org/hc/en-us/articles/360007318591-Debug-Logs-and-Crash-Reports#:~:text=Steps%20to%20share%20a%20debug%20log%20if%20Signal%20Desktop%20does%20not%20open under the Desktop > "Steps to share a debug log if Signal Desktop does not open" section? — Reply to this email directly, view it on GitHub <#6803 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAWKZPJY47H5YZGJZIIQSTZLWGPBAVCNFSM6AAAAABD233IZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRRGMYTGNJUG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[indutny-signal]

@AJolly could you compress them (they should compress really well), and send them over to [email protected] while mentioning the github issue, please?

Thank you so much!

[AJolly]

60mb each, I uploaded them / sent you guys an e-mail.

@AJolly could you compress them (they should compress really well), and send them over to [email protected] while mentioning the github issue, please?