search

bitwarden / android

Bitwarden mobile app for Android.
https://bitwarden.com
GNU General Public License v3.0
6.55k stars 821 forks source link

Vault gets stuck on loading after unlocking #3881

Closed antiquely8637 closed 2 weeks ago

antiquely8637 commented 2 months ago

Bitwarden Beta

Steps To Reproduce

  1. Tap on a login field.
  2. Unlock app with PIN or biometrics.

Expected Result

List of saved login items is shown.

Actual Result

App gets stuck on a loading circle. Force closing the app fixes the issue for a while.

Screenshots or Videos

Screenshot_20240907-104017

Additional Context

No response

Build Version

2024.8.1-beta (19099)

Environment Details

Pixel 8 Pro on Android 14.

Issue Tracking Info

bitwarden-bot commented 2 months ago

Thank you for your report! We've added this to our internal board for review. ID: PM-11753

antiquely8637 commented 2 months ago

Found other reports of this issue https://community.bitwarden.com/t/bitwarden-window-stuck-loading-indefinitely-when-autompleting-after-unlocking-with-pin/ https://community.bitwarden.com/t/vault-does-not-appear-after-unlocking/ https://old.reddit.com/r/Bitwarden/comments/1excplv/updated_app_sometimes_just_gets_stuck_loading/

SergeantConfused commented 2 months ago

Hello @antiquely8637,

Thank you for bringing this to my attention.

  1. How many matching vault items are displayed when you do unlock Bitwarden successfully?
  2. Does this happen only when you unlock the vault via a PIN? Are you able to reproduce this whilst unlocking the vault via the master password or biometrics?
  3. Are you logged into more than one Bitwarden account via that Bitwarden Android client?
  4. Could you please detail your KDF configuration?

For added context, I am unable to reproduce this on a Pixel 5 running Android 14 with Bitwarden 2024.8.0 by attempting to perform autofill with 1 matching vault item within Chrome whilst I am logged into a single Bitwarden account.

Thank you in advance,

antiquely8637 commented 2 months ago

Hi @SergeantConfused

  1. How many matching vault items are displayed when you do unlock Bitwarden successfully? When it successfully unlocks, I can see all saved matching items properly. Can be 1 or more depending on the specific website. The app hangs irrespective of how many matching items are in the vault.

  2. Does this happen only when you unlock the vault via a PIN? Are you able to reproduce this whilst unlocking the vault via the master password or biometrics? Happens with both PIN and biometrics (fingerprint and face unlock).

  3. Are you logged into more than one Bitwarden account via that Bitwarden Android client? Only one account.

  4. Could you please detail your KDF configuration? Argon2id 64 MB memory, 3 iterations and 4 threads. I have tried changing back to PBKDF2 with 600 000 iterations, but that did not fix it.

I've noticed that the app hangs after the it times out in the background. Try setting a 1 minute session timeout, let the app lock itself in the background, and try to autofill within chrome.

fredgolightly commented 2 months ago

Happening here too on all devices using 2024.8.0 (18985)

flo-m commented 2 months ago

same here, after autofill unlocking with biometrics - only loading circle is shown. Force Close Bitwarden Beta 2024.8.1 and starting again brings up the vault within a second.

dfunkt commented 2 months ago

@SergeantConfused: Managed to get some logs for you (Version 2024.8.1 (19099))

09-11 19:29:50.395 22330 22330 E ActivityImpl: get life cycle exception
09-11 19:29:50.395 22330 22330 E ActivityImpl: java.lang.ClassCastException: android.os.BinderProxy cannot be cast to android.app.servertransaction.ClientTransaction
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.ActivityImpl.checkAccessControl(ActivityImpl.java:64)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.ActivityImpl.onResume(ActivityImpl.java:140)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.Activity.onResume(Activity.java:2128)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at i.i.onResume(Unknown Source:5)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1592)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.Activity.performResume(Activity.java:8741)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.ActivityThread.performResumeActivity(ActivityThread.java:5079)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:5122)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:54)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.ClientTransactionHandler.executeTransaction(ClientTransactionHandler.java:64)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.ActivityThread.handleRelaunchActivityLocally(ActivityThread.java:6064)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2436)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.os.Handler.dispatchMessage(Handler.java:106)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.os.Looper.loopOnce(Looper.java:211)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.os.Looper.loop(Looper.java:300)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at android.app.ActivityThread.main(ActivityThread.java:8503)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at java.lang.reflect.Method.invoke(Native Method)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:561)
09-11 19:29:50.395 22330 22330 E ActivityImpl:  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
09-11 19:29:50.397  4743  4743 W RecentsImpl: onResumed className=com.x8bit.bitwarden.MainActivity   mIsInAnotherPro=false   isKeyguardLocked=false   mSecuritySpaceGuideShown=false
09-11 19:29:50.398  4743  4830 W RecentsImpl: disableTouchBySwipeStatusBar    disable=false
09-11 19:29:50.398  4743  4830 W RecentsImpl: disableBackStubWindow    disableTouch=false

Steps to reproduce:

  1. Create entry for a site to auto-fill
  2. Enable Auto-fill services
  3. Set session timeout to 1 minute
  4. Try to auto-fill entry via Gboard's inline auto-fill in Chrome after the timeout value is reached
Issam28 commented 2 months ago

@SergeantConfused, I can reproduce this bug following these steps:

  1. Open the bitwarden vault and keep the app oppened in the background.
  2. Go to chrome and auto fill from any website
  3. The vault will hang forever.

For testing purposes, I set the vault timer to "immediately" but the bug can be reproducible by any timer. I'm using a Pixel 8 on Android 15 beta.

Here's a video that shows how it works.

https://github.com/user-attachments/assets/535f9c59-2d5f-4429-9837-cb67d6adab68

dragm83 commented 2 months ago

Same issue on a Galaxy S23 Ultra running 2024.8.1 (beta).

MillionsToOne commented 2 months ago

+1

SergeantConfused commented 2 months ago

Hello everyone,

Thank you all for your input. I was able to reproduce this now on a Pixel 5 running Android 14 with Bitwarden 2024.8.1, and have highlighted this internally to the Engineering department. Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

Thank you all again,

johnkennyuk commented 2 months ago

Also affected by this bug. Reverted to prebeta because of this bug and missing feature #3766

SohamJ commented 1 month ago

One workaround I've been using is to open the app again and then go back to autofill. That avoids the need to force close the app.

antiquely8637 commented 1 month ago

Just tried a clean install of 2024.9.0 (19209). Bug still there.

flo-m commented 1 month ago

What works for me as a temporary workaround ist to set the Energy saving feature for bitwarden app to max - so that the App will be closed instantly. Then Autofill works fine and the bug ist Not there...

tykisson commented 1 month ago

App Version 2024.9.0 still an issue. Did find if I open/unlock Bitwarden first then go to app and use autofill it will search properly with out just sitting there spinning.

ghanjiboy commented 1 month ago

I am also experiencing the same issue. I have only had the beta installed since around September 10th. This spinning behavior wasnt happening then, but started happening about a week or so ago. I am experiencing the same as others above with spinning right after initiating autofill and unlocking.

If I unlock the app and then goto autofill, everything works, the app opens and presents the handful of choices.

I am running 9.0 as well.

laxmanpradhan commented 1 month ago

I have the same issue on 2024.9.0 installed via obtainium on a google pixel 8.

I'm connecting to a self hosted vaultwarden if that matters. Happy to update with logs, I just don't know how to get logs for the android app.

The same workaround above works for me. This is only an issue when Bitwarden is opened via autofill prompt from the browser. When I force close it and open Bitwarden directly it works without issue.

Bims-sh commented 1 month ago

Same problem here on 2024.9.0, Android 15

Opening the app from my home menu and going back to auto-fill in my browser makes it load and work for some time :+1:

cs-manughian commented 1 month ago

I'm running v2024.6.2 and experiencing the same issue on the desktop app on Windows 10. Inputting my password loads indefinitely and it never unlocks.

laxmanpradhan commented 1 month ago

FWIW clearing the cache and relogging into the app fixed it for now. I'll report back on if it happens again. Could be an error that takes a few days to show up

RickPJ commented 1 month ago

App Version 2024.9.0 still an issue. Did find if I open/unlock Bitwarden first then go to app and use autofill it will search properly with out just sitting there spinning.

I can confirm this behaviour (same app version).

In addition, after attempting to open for autofill, using fingerprint, and getting to spinning circle, if I then back out to the page I'm trying to fill, then open BW normally, it opens and is unlocked (i.e. the previous fingerprint succeeded).

Then, back on the page I want to fill, I can open for autofill and there is no delay.

ralob commented 1 month ago

App Version 2024.9.0 still an issue. Did find if I open/unlock Bitwarden first then go to app and use autofill it will search properly with out just sitting there spinning.

I can confirm this behaviour (same app version).

In addition, after attempting to open for autofill, using fingerprint, and getting to spinning circle, if I then back out to the page I'm trying to fill, then open BW normally, it opens and is unlocked (i.e. the previous fingerprint succeeded).

Then, back on the page I want to fill, I can open for autofill and there is no delay.

This is the same thing I experience with Android 14 and BW version 2024.9.0 (19209).

Additionally, sometimes I have to force close BW and reopen it to get autofill to work for the page I'm on.

bluearcher-bc commented 1 month ago

Additionally, sometimes I have to force close BW and reopen it to get autofill to work for the page I'm on.

@ralob switch from your browser/app you are trying to auto fill over to Bitwarden, then do a sync on the vault, then switch back to the app

Bims-sh commented 1 month ago

Same problem here on 2024.9.0, Android 15

Opening the app from my home menu and going back to auto-fill in my browser makes it load and work for some time 👍

For the past week this problem somehow went away for no reason, I have not changed any settings on my phone that could have fixed this as far as I'm aware.

niikoo commented 1 month ago

Additionally, sometimes I have to force close BW and reopen it to get autofill to work for the page I'm on.

@ralob switch from your browser/app you are trying to auto fill over to Bitwarden, then do a sync on the vault, then switch back to the app

This works as a workaround, but it's very annoying that I have to do that all the time.

Currently running Bitwarden version 2024.9.0 (19209) on Android 15 QPR Beta 2 (Pixel 6).

leo-liar commented 3 weeks ago

Problem unfortunately still not fixed with recently released stable build 2024.10.1 ...

(As workaround I'm doing what bluearcher-bc recommended a few days ago.)

Edit: With 2024.10.2 this seems to be fixed now! Seems to have been a fluke because the bug is occurring again :/

OnePlus 8T on LineageOS 20 (Android 13)

ghanjiboy commented 3 weeks ago

With the latest beta and now the official release, both are now working as expected for me.

maszaa commented 3 weeks ago

Exists in 2024.10.2 which seems to be the latest official version.

Ices-Eyes commented 3 weeks ago

Hi, same problem here with the official version released this days 2024.10.2 on Oneplus Nord 2 with android 13.

RickPJ commented 3 weeks ago

I'm now on 2024.90, and the autofill tile doesn't work at all. Even when on a field and URL for which I know BW has an entry, tapping the tile does nothing. Force closing BW doesn't fix it. FairPhone 3, AOS 11

masterflitzer commented 3 weeks ago

@RickPJ can you try on 2024.10.1 or even 2024.10.2? it's fixed for me currently (no problems for 1 day)

MillionsToOne commented 3 weeks ago

@RickPJ can you try on 2024.10.1 or even 2024.10.2? it's fixed for me currently (no problems for 1 day)

I believe it will be mentioned in the changelog once it's fixed.

RickPJ commented 3 weeks ago

Where can I download the APK? Currently I'm just getting beta updates from the Play store, latest there is 2024.9.0

MillionsToOne commented 3 weeks ago

Where can I download the APK? Currently I'm just getting beta updates from the Play store, latest there is 2024.9.0

Github releases

jannispl commented 3 weeks ago

Can confirm the issue still exists in 2024.10.2 (and current main branch at c2537f329d573209f065138cd37dd151471ee912).

flo-m commented 3 weeks ago

Maybe you guys use vaultwarden?

dfunkt commented 3 weeks ago

It's just not fixed yet, there's a PR in progress for it -> https://github.com/bitwarden/android/pull/4214

pcartwright81 commented 3 weeks ago

Maybe you guys use vaultwarden?

Not sure why this suggestion was thumbs-downed. In reality I have dealt with this bug for at least the last 2 months on the beta version, and now it has been released to the masses. This is a breaking issue for me because I can not rely on my phone to work correctly. I try to auto fill and get stuck in this loop that requires killing the app multiple times. I could have gone back to the stable version before, but the issue would catch up sooner or later, and I didn't realize it would take 2 months to fix.

Currently I am looking into vaultwarden or a self hosted instance with a client version that I know to be stable.

This was especially fueled by the fact that I had to clear storage as soon as version 2024.11.0 was installed today because of an app crash.

NotoriousNico commented 2 weeks ago

I have the exact same issue on all of my devices (for example my Samsung Galaxy S24 Ultra running Android 14).

I'm using Version: 2024.10.2 (19397) and have not a self-hosted Bitwarden instance. The issue happens also regardless of what browser or App I'm using.

In its current state, Bitwarden for Android is almost useless for me, and I'm quite perplexed that this issue made it into Stable.

I hope this gets resolved soon.

dannyglover commented 2 weeks ago

Version 2024.11.0 (19421) seems to have made this issue occur even more frequently.

I'm really hoping that the issue is fixed soon, as it's quite infuriating.

Thank you.

AT181903 commented 2 weeks ago

Same problem here with last version (2024.10.2). The problem occurs when I autofill from browser. To solve the issue I have to open the main app and manually sync, but next time the problem occurs back.

fredgolightly commented 2 weeks ago

This is happening even more with the newest Play Store update on all my and my family devices, absolutely unusable now especially for those without much tech knowhow as it requires closing BW, opening the app settings, force closing it, reopening the app/website then BW.

RickPJ commented 2 weeks ago

My phone has just updated to 2024.11.1 via the Play store, and I can report that the BW quick tile is now working correctly. 🙂

bluearcher-bc commented 2 weeks ago

@RickPJ don't get ahead of yourself, the PR that should resolve this is still open. This issue doesn't always show up right away after an update.

AT181903 commented 2 weeks ago

Updated to 2024.11.1, the problem persists when auto filling from browser

Secunda-Moon commented 2 weeks ago

Thought something wrong with my internet connection, but things turned out that it is a widely-encountered software bug. I'm still experiencing this problem with the latest beta version. Tried the regular version, and the problem remains.

Hope the developer can fix the bug.

dfunkt commented 2 weeks ago

For those that can't wait for an update, there are builds available now with commit ec85e7af619a755720f91caaef994a7913919325 that appears to fix this behaviour -> https://github.com/bitwarden/android/actions/runs/11712269067

maxmini1 commented 2 weeks ago

For those that can't wait for an update, there are builds available now with commit ec85e7a that appears to fix this behaviour -> https://github.com/bitwarden/android/actions/runs/11712269067

@dfunkt Hi there thank you su much for the update its seem to have fixed on Version: 2024.11.2 (19430. new its work perfect keep up the great work!

https://github.com/user-attachments/assets/8f39afee-b2f1-4975-ba8a-b2d790501acb

YamiYukiSenpai commented 2 weeks ago

When will that update get pushed to the stable or beta version in F-Droid?