touch-packages team mailing list archive

[David Barth <david.barth@xxxxxxxxxxxxx>]

A few more observations from our debug session.

I can reproduce the issue with a backup of my tokens. I had removed .local/share/com...webapp-gmail, and once restarting Gmail the app was starting straight on the login.ubuntu.com page, asking for my user/pass.
The issue is that after validating correct user/pass creds, the new URL on login.ubuntu.com is not accepted by the container and re-opened in the browser.

On further inspection, the .config/com...webapp-gmail file which should
contain the URL for login.ubuntu.com was not containing it.

This means that the SAMLRequest was never being seen by the container
code. Otherwise, it would have added it in the config file.

Others tried to reproduce the problem with my own credentials backup,
but in there case the app was opening on the initial Google login
screen, not the 2nd login screen managed by Ubuntu.

Finally, I tried removing not only .local/share but also my .cache/com
...webapp-gnail directory.

This resulted in the app opening on the initial Google login screen, not
the ubuntu one. And as a result, when entering my username on this
initial screen and validating, the subsequent SAMLRequest was properly
detected and I was able to login and proceed to the Gmail inbox screen
without issues nor browser re-directs.

So this indicates that the webapp cache, ie webapp-container/oxide
cache, contains something like the last URL navigated to. And on app
startup, the webview is directly and silently redirected there, without
any onNavigationRequest signal being fired. This prevents the
SAMLRequest pattern from being detected, and leads to the browser re-
directs creating the quite messy user experience.

At this stage,  we are looking for the cause for this cache and .config
file to be out of sync. Normally, if ever the cache contains a
login.ubuntu.com url, it should be as a result of an initial login,
which should have been detected and added to the .config file.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1517102

Title:
  Gmail webapp account renewal not successful

Status in The Webapps-core project:
  New
Status in webapps-sprint:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  MX4 running rc-proposed 167

  I ran the gmail webapp which I have done in the past.
   I had a google account configured, and gmail was permitted to use it

  Open gmail, get directed to login with ubuntu one
  login into ubuntu one
  redirect to a webbrowser instance with my google account home displayed and no option for mail
  Close the browser
  the ubuntu one screen is still up but has no navigation available, so close that too
  close the gmail webapp

  I repeated that entire thing more than once, but third time I reopened
  the webapp it showed me the mail using my account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-core/+bug/1517102/+subscriptions