1459594 - Login stops working when the site is installed as a PWA (works on chrome)

Status: RESOLVED MOVED

(Web Compatibility :: Site Reports, defect, P1)

Description

[Levente Sacal]

Device(s):
 -  Sony Xperia Z5(Android 7.0);


Build(s):
 - Nightly 61.0a1 (2018-05-06);
 - Beta 60.0
 - Release 59.02


Steps to reproduce:
 1. Add Pinterest to homepage as PWA.
 2. Log into Pinterest PWA using gmail credentials.
 3. Wait until the log in screen appears.

Expected result:
-Log in successfully into Pinterest.


Actual result: 
-Log in screen remains blocked.


Notes:

- when tapping on the Close button from the web app stuck log in screen, then clicking on the Connect with Google and clicking once again on the Close button from the stuck log in screen, you will be redirected to the Pinterest home and the user is logged in.

- the issues only happen when logging in for the first time. afterwards the user can log in and log out successfully


https://www.youtube.com/watch?v=NpVdWSq4Qw0&feature=youtu.be

Comment 1

[Levente Sacal]

This issues also happens with other PWA such as Flipboard when trying to log in using Gmail.

Comment 2

[Kevin Brosnan [Ex-Mozilla]]

Assuming this is webcompat, it sounds like something to discuss on the Mozilla-Google mailing list.

Comment 3

[Mike Taylor [:miketaylr]]

Sergiu, does this reproduce for you? It's working for me successfully on the first time (even after clearing cookies, etc). I wonder if it's locale sensitive.

Comment 4

[Sergiu Logigan [:sergiu]]

Yes, I can reproduce this issue consistently.
I cleared the app's data prior to running the test.

The issue is also reproducible with PWA created from Chrome Mobile. http://prntscr.com/jf6ce4

Tested on Huawei P10, Android 7.0, Nightly 61 and Chrome 66, with and without US VPN connection active.

Comment 5

[Mike Taylor [:miketaylr]]

OK, if this happens to Chrome Mobile as well, there's not much we can do beyond let Google(?) Pinterest(?) know.

Comment 6

[Levente Sacal]

Further to this issue I am unable to log into Flipboard at all with my Gmail or FB account. After trying to log in for the first time with Gmail/FB account, the option to try and log in again with these options is greyed out and the workaround cannot be performed.

https://youtu.be/94COBhx_RCs

Comment 7

[Levente Sacal]

Also unable to register using the Imgur web app. After tapping on the register option in web app, the screen remains stuck in a white background. Afterwards you can't access imgur.com from the browser either.

https://youtu.be/BHP2mxAxguI

Comment 8

[Liz Henry (:lizzard) (relman/hg->git project)]

Not a new regression but may be a useful bug for the geckoview team. Snorp is this addressed already?

Comment 9

[Chris Peterson [:cpeterson]]

Removing [geckoview] whiteboard tag because this is not a Gecko bug.

Comment 10

[Oana Arbuzov [:oanaarbuzov]]

For Pinterest: the issue still occurs on Firefox, indefinite spinner displayed, but on Chrome login is successful.
https://prnt.sc/10p34rt

For Imgur: login is no longer available (removed)
https://prnt.sc/10p39ls

For Flipboard: the issue still occurs on Firefox, indefinite spinner displayed, but on Chrome login is successful.
https://prnt.sc/10p3bqn

Tested with:
Browser / Version: Firefox Nightly 210317 (🦎 88.0a1-20210313094300)
Operating System: Samsung Galaxy S8 (Android 9) - 1440 x 2960 pixels, 18.5:9 ratio (~570 ppi density), Google Pixel 5 (Android 11) - 1080 x 2340 pixels, 19.5:9 ratio (~432 ppi density)

Comment 11

[Raul Bucata]

The issue is still reproducible on my side:

https://prnt.sc/8lora6WAlFf5

Tested with:

Browser / Version: Firefox Nightly 100.0a1 (2015870571 -🦎100.0a1-20220323094932🦎)
Operating System: Samsung A51 (Android 11) -1080 × 2400 pixels 20:9 aspect ratio (~405 ppi density)
Operating System: Google Pixel 3 (Android 12) -1080 x 2160 pixels, 18:9 ratio (~443 ppi density)

Comment 12

[Chris Peterson [:cpeterson]]

Raul, do we know whether this is a bug in Firefox Android or the websites?

I see that I said in comment 9 (three years ago!) that this is not a Gecko bug, but I don't remember what evidence I had to support that claim. :)

Comment 13

[Raul Bucata]

Hi Chris. For me, this is a bug replicating only on Firefox, Chrome works as expected. However, this replicates only using the PWA feature (adding Pinterest to the home screen via the "Add to Home screen" option of the browser). Using the browser without this feature works as expected.

Comment 14

[Karl Dubost💡 :karlcow]

At least we can all agree.

• This is happening on a multiple sites
• This is working on Chrome.
• The pattern is: Add a website as a PWA on the mobile, then try to login from the PWA. (I wonder if there is something related to opening separate windows for login)
• The login is working when directly done in the browser instead of the PWA

I think it would need to be look at by Core Engineers because the behavior changes depending if it's inside PWA or browsers.

Chris, where should we move to have the right pair of eyes to look at the possible bug. I'm not sure how to diagnose this once the PWA has been installed.

Comment 15

[[ex-Mozilla] Agi Sferro | :agi]

I think this actually a Fenix/AC bug, specifically a consequence of https://github.com/mozilla-mobile/android-components/issues/11759

I see an error on one of the two duplicated windows related to window.opener being null, which would make sense because only one of the two windows can be the one created in response to window.open so GeckoView wouldn't set the opener on the other one.

Comment 16

[Chris Peterson [:cpeterson]]

(In reply to Agi Sferro | :agi | [slow ni? rn sorry] | ⏰ PST | he/him from comment #15)

I think this actually a Fenix/AC bug, specifically a consequence of https://github.com/mozilla-mobile/android-components/issues/11759

I see an error on one of the two duplicated windows related to window.opener being null, which would make sense because only one of the two windows can be the one created in response to window.open so GeckoView wouldn't set the opener on the other one.

In that case, I'll follow up with the Fenix team.

Here is the corresponding Fenix Jira issue: https://mozilla-hub.atlassian.net/browse/FNXV2-19607

Comment 17

[Dennis Schubert [:denschub]]

This is caused by the aforementioned Fenix/Android-Components issue, let's close this bug as MOVED towards the issues in Comment 15 and Comment 16.