Issue metadata
Sign in to add a comment
|
Android Apps in ChromeOS trigger Facebook login in main browser, then don't link back correctly
Reported by
iko...@gmail.com,
Jul 15
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS aarch64 10575.58.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Platform: 10575.58.0 (Official Build) stable-channel elm Steps to reproduce the problem: 1. Open an Android app with Facebook login, e.g. WeChat 2. Try logging in with Facebook What is the expected behavior? The login can happen in either the main window, embedded window, or Facebook app What went wrong? (In this case I don't have the Facebook app installed) A blank embedded browser shows, while the link opens in the main browser window, correctly handles the login, then tries to do a callback, which triggers an error because of a not recognized protocol, and the app with the blank embedded browser never proceeds, thus not enabling logging in. Did this work before? Yes not sure (version before the embedded browser moved to the main window) Chrome version: 67.0.3396.99 Channel: n/a OS Version: 10575.58.0 Flash Version: 30.0.0.113
,
Jul 16
Same thing happens with e.g. Audible app with Amazon login |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Jul 16