1Password for iOS and Westpac Mobile Banking

aussiecrocodile
aussiecrocodile
Community Member
edited November 2015 in iOS

Dear AgileBits team,

I am experiencing difficulties auto filling Customer ID and Password fields on the Westpac Mobile Banking website. Instead of inserting my username into the Customer ID field, 1Password for iOS inserts my password into it, though the app leaves the password field empty.

I tried to delete and create another login manually, but it did not help.

I would be grateful if you could check and fix this issue.

Sincerely yours,
Aussie Crocodile


1Password Version: 6.0.2
Extension Version: N/A
OS Version: iOS 9.0 (13A343)
Sync Type: Dropbox

Comments

  • Rad
    Rad
    1Password Alumni

    Hi @aussiecrocodile,

    Thanks for taking the time to write in :+1:

    How did you manually re-create the login? I successfully created a "dummy" login for https://online.westpac.com.au/esis/Login/SrvPage?app=mobile using Safari and the 1Password App Extension (VPN for Australia was necessary :wink: ). Here are the steps I took to do so:

    • Went to https://online.westpac.com.au/esis/Login/SrvPage?app=mobile on my iPad.
    • Typed a "dummy" username using the keyboard.
    • Typed a "dummy" password using the on-screen keyboard.
    • Called the 1Password App Extension and tapped on the "New Login" button. The username and password were the same as the ones that I previously typed.
    • Tapped on save.
    • I reloaded the page to clear the username and the password fields.
    • Called the 1Password App Extension again and successfully filled using the newly created login.

    Hope that this helps :smile:

    Cheers!

  • aussiecrocodile
    aussiecrocodile
    Community Member
    edited November 2015

    Hi @Rad

    Thank you for your prompt response.

    The steps work indeed! I did not notice the "New Login" button before.

    The way I did it:
    1. Opened 1Password for iOS on my iPhone
    2. Categories → Logins → +
    3. Login name: Westpac Mobile
    4. Username: xxx
    5. Password: yyy
    6. Tapped on Save
    7. Tapped on Edit
    8. Entered the website address https://online.westpac.com.au/esis/Login/SrvPage?app=mobile
    9. Tapped on Done
    10. Tapped on the address, the in-app browser opened the website
    11. The Customer ID field contained the password

    Cheers!

    Update:
    I opened the website in Safari on my iPhone, called the 1Password App Extension, tapped the manually created login Westpac Mobile, and the form was populated correctly.

    Looks like there is an issue in the in-app browser only.

    Could you try my steps and check if the issue reproduces on your iPad.

    Thanks for your help!

    Regards,
    AC

  • Perfect. Glad to hear that worked. :)

    If there is anything else we can do, please don't hesitate to contact us.

    Ben

  • aussiecrocodile
    aussiecrocodile
    Community Member
    edited November 2015

    Hi @bwoodruff , @Rad

    Looks like the issue persists in the in-app browser only.

    Credentials saved by the "New Login" button do not insert correctly into the login form in the in-app browser.

    Steps:
    1. Follow steps 1 to 5 from @Rad's comment
    2. Open 1Password for iOS
    3. Change the password to the correct one. For some reason the 1Password App Extension saved it as !!!!!!
    4. Tap on the website address inside the application. The in-app browser, not Safari, should load the page
    5. The Customer ID field contains the password

    Regards,
    AC

  • Rad
    Rad
    1Password Alumni

    Hello again @aussiecrocodile,

    Thanks for isolating the issue to 1Browser :+1:

    I was able to reproduce the problem here and I filed an internal bug in our issue tracker.

    If there's anything else we can do for you, please do not hesitate to ask :wink:

    Best,

    ref: OPX-1076

  • aussiecrocodile
    aussiecrocodile
    Community Member

    Hi @Rad,

    Thank you for your help!

    Best regards,
    AC

  • Rad
    Rad
    1Password Alumni

    Cheers @aussiecrocodile :+1:

    Rad

This discussion has been closed.