Details view stuck at the "Loading please wait" screen for entries with TOTP

[AdamantGarth]

General information

• Operating system + version: Arch Linux
• Browser + version: Chromium 126.0.6478.126
• Information about the host app:
  • How did you install it?
    Via the package manager.
• Information about the browser extension:
  • How did you install it?
    Via the package manager.
  • Browserpass extension version as reported by your browser: 3.8.0

Exact steps to reproduce the problem

1. Open the extension popup.

2. Open the details of an entry that has an otpauth: field.

What should happen?

The entry details are shown.

What happened instead?

The "Loading please wait ..." message is displayed indefinitely.

Additional notes

• Entries without TOTP work fine.
• The OTP code gets copied to the clipboard after filling the credentials, so the extension is able to read those entries.

[AdamantGarth]

When this happens, Chromium prints the following line to the logs:

INFO:CONSOLE(49256)] "Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'type')", source: chrome-extension://pjmbgaakjkbhpopmakjoedenlfdmcdgm/js/popup.dist.js (49256)

Line 49256 points here, which seems relevant:

browserpass-extension/src/popup/detailsInterface.js

Line 169 in dc71d47

login.fields.otp.params.type === "totp"

Edit: the otpauth entry I test this with starts with otpauth://totp/, so the type is there.

[creepiepanda]

I can confrim this issue on my side with the same error in the console / logs.

OS: Debian 12
Browser: Google Chrome Version 127.0.6533.17 (Official Build) beta (64-bit)
Browserpass: 3.8.0 from chromewebstore

[erayd]

@AdamantGarth Could you please post the entirety of that line of your password file, with the secret redacted? I suspect the issue is being triggered by the way that line is formatted, and not by TOTP entries generally (testing with totp: SECRETKEY style lines works just fine).

[AdamantGarth]

Sure, here it is:

otpauth://totp/Google%3Ausername%40gmail.com?secret=redacted&issuer=Google

It also reproduces on entries with otpauth URLs that have all of the optional parameters specified, like:

otpauth://totp/website:username?secret=REDACTED&period=30&digits=6&issuer=website

[jirib]

@AdamantGarth Could you please post the entirety of that line of your password file, with the secret redacted? I suspect the issue is being triggered by the way that line is formatted, and not by TOTP entries generally (testing with totp: SECRETKEY style lines works just fine).

I think you point to the right thing but it is not clear; what is the format of OTP line needed in the password file, please? See https://github.com/tadfisher/pass-otp?tab=readme-ov-file#migrating-from-pass-otp-01 .

My pass entry format is the following:

<password>
otpauth://totp/<url>%3A<username>?period=30&digits=6&algorithm=SHA1&secret=<secret>&issuer=<issuer>

[evok01]

Just wanted to put it out there in case anyone else came to this issue like I did because I suddenly had this exact issue now (same error and line that @AdamantGarth pointed out) without realizing the extension was updated recently:

As referred to in #368, try adding back your custom store location as that is what fixed this for me after the update.

[Neowizard]

Just wanted to put it out there in case anyone else came to this issue like I did because I suddenly had this exact issue now (same error and line that @AdamantGarth pointed out) without realizing the extension was updated recently:

As referred to in #368, try adding back your custom store location as that is what fixed this for me after the update.

I have no idea why this fix works, but it did for me. Just set the custom store full path in the browserpass extension preferences, and passwords with OTP now work.

Thanks