Open Bug 1913727 Opened 3 months ago Updated 7 days ago

welcometomygarden.org - Account login fails on Android devices with ETP set to STRICT

Categories

(Web Compatibility :: Privacy: Site Reports, defect, P3)

Firefox 129
Other
Android

Tracking

(firefox129 affected, firefox131 affected)

Tracking Status
firefox129 --- affected
firefox131 --- affected

People

(Reporter: rbucata, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: priv-webcompat, webcompat:needs-diagnosis, webcompat:site-report, 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)

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:

  1. Navigate to: https://welcometomygarden.org/sign-in
  2. Introduce valid credentials and tap on the "Sign in" button
  3. 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

Severity: -- → S2
User Story: (updated)
Priority: -- → P3
Flags: needinfo?(wwen)

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.

Flags: needinfo?(wwen)
Component: Site Reports → Privacy: Site Reports

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.

Raul, William mentioned that this is no longer reproducible. Could you verify it again?

Flags: needinfo?(rbucata)
Keywords: priv-webcompat

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)

Flags: needinfo?(rbucata)
Attached image STANDARD vs STRICT
Flags: needinfo?(wwen)

(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.

Summary: welcometomygarden.org - Account login fails on Android devices with ETP set to STANDARD → welcometomygarden.org - Account login fails on Android devices with ETP set to STRICT

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.

Flags: needinfo?(wwen)

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?

Flags: needinfo?(valentin.gosu)

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.

Flags: needinfo?(valentin.gosu)
Severity: S2 → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: