[BUG] Cloudflare captcha always failure in app, but on a browser it works

[n-core]

Describe the bug
Is it just me or the Cloudflare captcha always failed to check when in app?
I can't download/update everything through androidacy web through the app. I need to go to external browser to download it and the captcha automatically success.

Is there something wrong within the app or is it just my device?

To Reproduce
Steps to reproduce the behavior:

1. Try to download any module that leads androidacy site in app
2. Tap the captcha checkbox above the download button
3. Check if the captcha is successful or not

Expected behavior
Captcha success after you tap the checkbox.

Screenshots
Always failure when I open it in app

It instantly successful without having to tap the checkbox when I open it on a browser

Device info(please complete the following information):

• Device: Asus Zenfone Max Pro M1
• OS: Stock ROM on Android 9 (Pie)
• App Version [the latest one on GitHub release]

Additional context
I use Firefox as a mainly browser. But when I try to change the default browser to Chrome it still the same thing.

[androidacy-user]

This is very interesting. We'll investigate the issue from our end, but it may require a solution from the vendor in which case it's out of our hands.

[Fox2Code]

Fix will be released on 0.6.6

[androidacy-user]

We've worked around the issue on our end by implementing HCaptcha instead of Turnstile temporarily and will continue to work with @Fox2Code and Cloudflare on a more proper resolution.

[NestaYor]

this is still happening. androidacy is the absolute worst. Why are they even a default, do you get a % of their monetization? if only they spent half as much time on hosting issues as they do monetization.

Problem for well over a month and instead of a solution they're pushing more ads and a premium feature (to host other people's hard work)

Their inclusion by default makes your exceptional project look bad. cut them out.

[androidacy-user]

this is still happening. androidacy is the absolute worst. Why are they even a default, do you get a % of their monetization? if only they spent half as much time on hosting issues as they do monetization.

Problem for well over a month and instead of a solution they're pushing more ads and a premium feature (to host other people's hard work)

Their inclusion by default makes your exceptional project look bad. cut them out.

Turnstile has been a success in our own internal testing and surveys, and we've worked around bugs we've found both on our end and FoxMMM's end. I apologize if this isn't the case for yourself.

Unfortunately, some users feel the need to use bots to spam our services so defenses like this are necessary. Bad apples ruin the experience for everyone.

Monetization has been explained many, many times and I'm not inclined to explain ourselves yet again.

Instead of insulting us and flame throwing, users like yourself are better off reporting bugs properly so they can be fixed instead of wasting time and trying to force others to do the same.

[Fox2Code]

@NestaYor this is very rude, I know you may not like Androidacy, and I respect your opinion, this is why I support you disabling their repo via the manage repo tab.

I agree that Androidacy has issues, but you are complaining for a service not being perfect and asked me to kick them out while you have no idea how much work and effort goes into a project like this.

Androidacy team put their heart and need the money to maintain their services, then even started making a program to make module creator win some money via the few extra bucks they have left after paying the server.

I'm not kicking them out of the app at all, if you are unhappy and want to kick them from your device just disable their repo in the settings of FoxMMM, it's your right to dislike a repo and not wanting to use it.

But your are not allowed to sabotage projects because it's not perfect or because it's not exactly how you like it.