[#5846] Remove custom user agent to fix captcha failure loop #5865
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
g1a55er
changed the title
|
I deleted the custom user agent in your way, but the problem still exists |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributor checklist
Description
I was also hit by the bug filed as #5846, where I get stuck in an infinite "Something went wrong" captcha failure loop on registration with notifications unavailable.
After some debugging, comparing iOS and Android, it turns out this traces back to hCaptcha not liking the custom user agent of the WebView used for the CAPTCHA view
Once I removed the custom user agent so that the WebView goes back to the default user agent, I am able to successfully get out of the failure loop.