Auto-fill does not work for Password Manager iOS action extension in Chrome browser
Reported by
andrei.s...@avira.com,
Dec 13 2016
|
|||||
Issue descriptionSteps to reproduce the problem: Hello, We currently have a Password Manager app and a Password Manager iOS Safari extension and would like to have that action extension working with Chrome too. Currently with Chrome browser: our extension is recognized, opened, I can obtain the URL information from Chrome payload (without using the "find-login-action" in the bundle name) and perform the extension logic. What is the expected behavior? We also need the autofill of login forms to work. What went wrong? I am sending the data back to Chrome like explained in: https://bugs.chromium.org/p/chromium/issues/detail?id=405894#c63 but nothing gets autofilled in the forms. For example, the 1Password iOS extension works for the LinkedIn login page (autofills the form), but our extension does not. Did this work before? N/A Chrome version: 55.0.2883.79 Channel: stable OS Version: 10.1.1 Flash Version: What am I missing from the picture? Do we need to let the Chrome team know of our app so that it can be whitelisted or something? Is "find-login-action" in the bundle name a mandatory requirement? (I am under the impression that it matters only when getting data from Chrome, but this is working for us). Is the payload I am sending wrong?
,
Dec 15 2016
,
Mar 14 2017
This is still the case. Google Chrome 57.0.2987.95 (Official Build) beta (64-bit) Revision 738ec999bea6... iOS 10.2
,
Mar 15 2017
Having "find-login-action" is mandatory. There are other feature requests ( issue 685094 and issue 681583 ) to make it easier because not all apps can change the bundle ID. I don't have a better solution than requiring specific substring in bundle ID or whitelisting bundle IDs in Chromium code (see comment 2 & 3 in issue 681583 ).
,
Mar 22 2017
,
Apr 23 2017
If you take a look at https://codereview.chromium.org/2820113002/, it is a one-line change. You can make the change and request a code review.
,
Apr 24 2017
Managed to solve the issue by using "find-login-action" in the bundle name and also making some changes in the return payload from extension to Chrome. So I think it can be closed.
,
Apr 24 2017
Thank you for the update! Marked as WontFix per comment 7. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by justincohen@chromium.org
, Dec 14 2016