Please fix PayPal 2FA auto-fill (bug: 6 identical digits)

I am happy to hear @"paul.m_1p" could come to the rescue when I could not recall the issue. Now I will forever associate this with you XIII and go looking though your comments if I need to dig it up again. ;)

Happy New Year as we inch closer to 2023.

Much to my surprise there were indeed 2 OTP's configured in my PayPal 1Password item...

Even more surprising: the "secret" for the second one was an invalid one, but 1Password was still generating TOTP codes from it...

Anyway, after removing that bogus second OTP everything seems to work as expected again 🎉

Thank you for helping me solve this after all this time!

Hey there XIII - Thanks for following up here 🙂

In the future, if we're asking for diagnostics to dig deeper, please email them into support@1password.com, along with the Community post URL, and your username. This way, we can ensure any information in the diagnostics can be kept private.

The console log doesn't look to be giving us anything useful related to the filling issue on this site, unfortunately. I've seen a couple other isolated reports of this behaviour, so I thought I'd share what has worked in those other user cases:

Checking if there are other one-time password fields in the item

If there is more than one one-time password field in the item, it can cause issues with autofill. To check this, open the 1Password app > search for the item and click 'Edit' > check to confirm there is only one 'one-time password' field showing. Here's a reference image when there are two:

If you do have a second one there, remove it, and try filling again.

Removing and re-saving the two-factor auth in the login item

1. Log into PayPal as normal.
2. Go into account settings, and disable 2FA.
3. Remove the one-time password field from the 1Password PayPal login item.
4. Re-enable 2FA and re-update your login item using this guide -> Use 1Password as an authenticator for sites with two-factor authentication
5. Save the settings on the PayPal page to ensure 2FA is set up once again.
6. Log out and log back in to test.

I hope some of this is helpful!

If it helps: it looks like the correct 6 digit code is filled in initially, but before that can be accepted by PayPal, the first digit is put in all six fields (overwriting the correct values).

Sorry, I'm not comfortable with sending a > 1 MB diagnostic report that's too large to inspect for privacy issues.

The extension console log seems not very helpful:


[Info] [BackgroundStorage] Using PersistentStorage (background.js, line 2)
[Info] [BackgroundStorage] Using MemoryStorage (background.js, line 2)
[Log] 👋 Initializing 1Password (background.js, line 2)
[Info] channel: stable (background.js, line 2)
version: 2.4.1
build: 20226 (16.2)
browser: Safari (16.2)
os: MacOSX (10.15.7)
[Info] 💫 Looking for desktop app com.1password.1password (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <REDACTED> (background.js, line 2)
[Info] 👍 Finished initializing 1Password (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <REDACTED> (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <REDACTED> (background.js, line 2)
[Info] We successfully unlocked 0 account(s) from a Desktop app with 0 unlocked and 1 locked account(s). (background.js, line 2)
[Info] 📤 Sending <NmShowUnlock> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <Nothing> from native core <REDACTED> (background.js, line 2)
[Info] Loaded page details in 12.999999999970896 ms. (background.js, line 2)
[Info] Analyzed the page in 2 ms. (background.js, line 2)
[Info] Received <LockStateChanged> from the native core (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <REDACTED> (background.js, line 2)
[Info] Received <LockStateChanged> from the native core (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <REDACTED> (background.js, line 2)
[Info] 📤 Sending <NmRequestAccounts> message to native core <REDACTED> (background.js, line 2)
[Info] Hooray!; Unlocked account REDACTED with MUK; 🎉 (background.js, line 2)
[Info] We successfully unlocked 1 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). (background.js, line 2)
[Info] [LM] Started Desktop Lock Monitor at REDACTED (Connected to desktop app). (background.js, line 2)
[Info] 📥 Received message <NmRequestAccounts> from native core <REDACTED> (background.js, line 2)
[Info] We successfully unlocked 0 account(s) from a Desktop app with 1 unlocked and 0 locked account(s). (background.js, line 2)
[Info] 📤 Sending <NmRequestDelegatedSession> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmRequestDelegatedSession> from native core <REDACTED> (background.js, line 2)
[Info] 📤 Sending <NmLockState> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmLockState> from native core <REDACTED> (background.js, line 2)
[Info] [LM] Started Desktop Lock Monitor at REDACTED (Connected to desktop app). (background.js, line 2)
[Info] 📤 Sending <NmLockState> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmLockState> from native core <REDACTED> (background.js, line 2)
[Info] [LM] Started Desktop Lock Monitor at REDACTED (Connected to desktop app). (background.js, line 2)
[Info] 📤 Sending <NmLockState> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmLockState> from native core <REDACTED> (background.js, line 2)
[Info] 📤 Sending <NmLockState> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmLockState> from native core <REDACTED> (background.js, line 2)
[Info] 📤 Sending <NmLockState> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmLockState> from native core <REDACTED> (background.js, line 2)
[Info] 📤 Sending <NmLockState> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmLockState> from native core <REDACTED> (background.js, line 2)
[Info] 📤 Sending <NmLockState> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmLockState> from native core <REDACTED> (background.js, line 2)
[Info] 📤 Sending <NmLockState> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmLockState> from native core <REDACTED> (background.js, line 2)
[Info] 📤 Sending <NmLockState> message to native core <REDACTED> (background.js, line 2)
[Info] 📥 Received message <NmLockState> from native core <REDACTED> (background.js, line 2)


Not sure why that OS (10.15.7) is listed; I run macOS Monterey Version 16.2 (17614.3.7.1.7, 17614).

Will try.

XIII are you able to reproduce the behavior and then send us the following so that we can investigate further?

• The extension console log: https://support.1password.com/cs/extension-console-log/
• A diagnostics report: https://support.1password.com/diagnostics/

Attach the logs and diagnostics to an email message addressed to support@1password.com.

With your email please include:
* A link to this thread: https://1password.community/discussion/134164/please-fix-paypal-2fa-auto-fill-bug-6-identical-digits#latest
* Your forum username: XIII

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks!

Still happens for me... (every time)

Current setup:

• macOS 12.6.2
• Safari Version 16.2 (17614.3.7.1.7, 17614)
• 1Password for Mac 8.9.11 (80911019)
• 1Password for Safari 2.4.1

XIII

Sorry no.

I still cannot reproduce this. On the Mac (13.0.1) I tried with Safari (2.4.1) and Chrome (2.5.0) while using both the button/inline menu and also Universal Autofill, all with no trouble. I switched to my phone and used (iOS 16.1.1) Safari browser and password autofill which also filled correctly. I also gave the Paypal app a go and when prompted to paste the 2fa code it worked without a hitch.

Are there any additional details you can provide me? I never located the previous issue I recalled. That said, I still hold firmly I saw something like this but I just cannot find it. Have you tried creating a new login, by chance?

• During my testing I used my personal account and I am in the US.

edit - fix wrong version number.

1P_Tommy Any update on this?