this post was submitted on 21 Sep 2023
33 points (100.0% liked)

Boost For Lemmy

7036 readers
1 users here now

Community of the Android app Boost for Lemmy Play Store Link

founded 1 year ago
MODERATORS
 

When attempting to add an account, no option to enter my TOTP authentication token is available.

Thanks for the hard work!

top 8 comments
sorted by: hot top controversial new old
[โ€“] [email protected] 9 points 1 year ago* (last edited 1 year ago)

Thanks for reporting, the 2FA field should show after pressing Login. I will take a look. Edit: Fixed for the next beta.

[โ€“] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

I experienced this as well but I was able to sign in somehow. Loving the app so far, so excited to test it out!

[โ€“] [email protected] 2 points 1 year ago (1 children)

Do you remember what you did?

[โ€“] [email protected] 2 points 1 year ago

For some reason when I entered my login information and clicked enter it just let me in. I was ready for the OTP but it never asked.

[โ€“] [email protected] 2 points 1 year ago

Same experience here. I tried the ol' paste it at the end and that didn't work either. I wouldn't doubt that there'll be an update addressing that once @[email protected] has a chance to update it.

[โ€“] [email protected] 2 points 1 year ago

Fixed in the latest version (1.0) :)

[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago)

As someone else said, this bug was fixed in the last versions (>1.0). However, I, personally, had problems with the 2FA code field not showing up because I was using the autofill from my password manager (1Password). Took a bit of experimenting to figure this out, but I just copied and pasted my username & password instead, and then everything worked normally. Just putting this here for whoever else might look at this post next with the same problem.

Also had another problem where my 2FA code was being generated with SHA1 instead of SHA256 as Lemmy uses, but that's probably because I set up 2FA way back, and it most likely wasn't specified properly.

[โ€“] [email protected] 1 points 1 year ago

Also having this issue.