I'm afraid that the attached logs are not relative to the first execution of the webapp, where the SAML login is performed.
#1 We do have this already, it's just a matter of copying the ~/.cache/online-accounts-ui/id-* files and restoring them.
#2 We also have useful debugging messages (and indeed, some less useful ones too) when the login happens; but in these logs we don't see them, because with all probability they are not the right log files.
I don't think that it's related to this bug at all, but there's a suspicious line in the logs:
Ignoring empty or invalid webapp URL pattern: "https?://accounts.google.co.*/*"
Indeed, the code in url-pattern-utils.cpp doesn't seem to support this kind or pattern, and that should be fixed.
I'm afraid that the attached logs are not relative to the first execution of the webapp, where the SAML login is performed.
#1 We do have this already, it's just a matter of copying the ~/.cache/ online- accounts- ui/id-* files and restoring them.
#2 We also have useful debugging messages (and indeed, some less useful ones too) when the login happens; but in these logs we don't see them, because with all probability they are not the right log files.
I don't think that it's related to this bug at all, but there's a suspicious line in the logs: ://accounts. google. co.*/*" utils.cpp doesn't seem to support this kind or pattern, and that should be fixed.
Ignoring empty or invalid webapp URL pattern: "https?
Indeed, the code in url-pattern-