welcometomygarden.org - Account login fails on Android devices due to TCP / dFPI
Categories
(Web Compatibility :: Privacy: Site Reports, defect, P3)
Tracking
(firefox129 affected, firefox131 affected)
People
(Reporter: rbucata, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: priv-webcompat, webcompat:site-report, webcompat:tracker-blocking, Whiteboard: [webcompat-source:product])
User Story
platform:windows,mac,linux,android impact:workflow-broken configuration:general affects:all branch:release diagnosis-team:privacy
Attachments
(1 file)
|
221.27 KB,
image/png
|
Details |
Environment:
Operating system: Android
Firefox version: Firefox 129.0 (release)/Nightly 131.0a1
Preconditions:
- ETP set to STANDARD
- Clean profile
- Account previously created
Steps to reproduce:
- Navigate to: https://welcometomygarden.org/sign-in
- Introduce valid credentials and tap on the "Sign in" button
- Observe
Expected Behavior:
Account login successfully performed
Actual Behavior:
The page is stuck in a loading state
Notes:
- Not reproducible with ETP turned OFF (both Normal and Private Browsing)
- Reproducible on the latest Nightly with ETP set to STRICT also
Created from webcompat-user-report:57724045-4832-43f7-ae43-77b77b01f08a
Updated•1 year ago
|
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Reproduced in ETP Standard and Strict in latest Nightly.
Browser console reports some issue with firebase authentication.
One interesting thing is that the tracking content button in the protections panel is not greyed out but reports no tracking content once clicked.
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Issue is no longer reproducible even in PBM/ETP Strict on Nightly and Release so looks like the website has fixed it. If someone can confirm we should be able to close this.
Comment 3•1 year ago
|
||
Raul, William mentioned that this is no longer reproducible. Could you verify it again?
| Reporter | ||
Comment 4•1 year ago
|
||
This reproduces for me now with ETP set to STRICT and works fine with ETP set to STANDARD
Tested with:
Browser / Version: Firefox Nightly 132.0a1 (2016044215-🦎132.0a1-20240913100931🦎)
Operating System: Google Pixel 3 (Android 12) -1080 x 2160 pixels, 18:9 ratio (~443 ppi density)
Operating System: Oppo Find X5 (Android 13) - 1080 x 2400 pixels, 20:9 ratio (~402 ppi density)
| Reporter | ||
Comment 5•1 year ago
|
||
Updated•1 year ago
|
Comment 6•1 year ago
|
||
(In reply to Raul Bucata from comment #4)
This reproduces for me now with ETP set to STRICT and works fine with ETP set to STANDARD
--> Adjusting bug title to reflect the updated situation.
Comment 7•1 year ago
|
||
Reconfirmed working on latest Nightly on ETP Strict on desktop (MacOS), seems like a mobile specific issue now. May look into it more but will need to setup my emulator first.
Comment 8•1 year ago
|
||
After some more testing, it seems that the behaviour is actually inconsistent regardless of ETP setting (Strict, Standard and Off) and platform. Sometimes it will work for ETP Strict and sometimes it will not work when ETP is off. Could be that this isn't related to ETP at all.
We noticed one network request to firestore.googleapis.com is taking a long time and can even fail sometimes. Could be that this is a network issue?
Comment 9•1 year ago
|
||
There seem to be some issues with firestore, but I'm not sure they are networking related. If I refresh the page again before logging in, it works.
I also see a bunch of these in the console: [2024-10-24T08:29:53.527Z] @firebase/app-check: AppCheck: Requests throttled due to 403 error. Attempts allowed again after 23h:59m:30s (appCheck/throttled).
I think this is application logic. I've also checked if this is related to service workers or http3 and it still didn't work if I disabled those.
Comment 10•11 months ago
|
||
This seems to reproduce intermittently on both Fenix Nightly and Release. That makes it really hard to troubleshoot and find the root cause.
The auth endpoint the site uses is a firebase iframe: https://wtmg-production.firebaseapp.com/__/auth/iframe(...) which receives only partitioned cookies. This suggests that it might be a dFPI / TCP issue.
I can't properly test this since, as mention in comment 9, Firebase throttles requests on network level and will not allow me to authenticate again when it previously failed.
Updated•7 months ago
|
Description
•