mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
2024.8 Beta app, unable to log in or sync #2003
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @turnah on GitHub (Aug 19, 2024).
Subject of the issue
Unable to sign into bitwarden app using version 2024.8.0 (beta) on android with 2FA.
Can confirm the webvault works as expected. no issues.
Attempted Yubikey, authenticator app code and email. Each one comes up with an error unable to validate.
Left the beta programme on android and rolled back to 2024.7.1 and all worked as expected.
Logging as a bug in case this is a breaking change on the android app - apologies if should be a discussion
Deployment environment
vaultwarden version: 1.32.0
Install method: docker
Clients used: android, webvault
Reverse proxy and version: caddy
Other relevant details:
Steps to reproduce
Join android beta, install 2024.8.0 and try to sign in (self hosted)
Expected behaviour
2FA validates
Actual behaviour
2FA unable to validate
@BlackDex commented on GitHub (Aug 19, 2024):
It works just fine for me.
Please provide logs which are generated during these attempts and if possible screenshots maybe of what you see.
Without that information we can't help.
Edit: I tested all options, WebAuthn (USB/NFC/Passkey via Other Bitwarden App), Fido2, Duo, Email and TOTP.
@turnah commented on GitHub (Aug 19, 2024):
The only line from the log is: [2024-08-19 10:42:55.196][error][ERROR] 2FA token not provided
Which seems pretty standard, as this appears when the 2FA screen pops up (before submitting)
The exact error on the app is "An error has occurred. Invalid verification code"
Once i attempt to log in, for example using yubi key and i get the above message i immediately get an email to say new device was logged in.
To confirm, this is on a Pixel 8 pro running android 14 (latest security/play system update) and bitwarden app: Version 2024.8.0 com.x8bit.bitwarden.beta
I'm running this side by side now with 2024.7.1 com.xbit.bitwaren which works as expected
I also removed all 2FA from my account and the beta app signed in as expected. Added the 2FA again and same issue
@BlackDex commented on GitHub (Aug 19, 2024):
I suspect that your reverse proxy is catching the error and returns it's own version.
The 2FA token not provided error contains a json which is used to provide all available 2FA options. As mentioned, it works fine for me, just tested all options a few minutes ago.
@turnah commented on GitHub (Aug 19, 2024):
I see, i've found the logs in caddy (which is setup as per the wiki) and looks like it's returning a 400:
I've removed the url and changed ip's below:
@BlackDex commented on GitHub (Aug 19, 2024):
A valid response to the client should look like below. Anything else will cause the clients to generate an error.
So, for us to see what might be the issue the exact same as i provided below.
I extracted this by using
tcpflow -i any -C port 8080which i run on the Vaultwarden host and i know this is forwarded 1:1 by my reverse proxy. But you need to know what the client receives.HTTP:
Body:
@BlackDex commented on GitHub (Aug 19, 2024):
Also, i see you are using Cloudflare, it might be that something there changes the response.
@turnah commented on GitHub (Aug 19, 2024):
Here is the tcp flow result:
@BlackDex commented on GitHub (Aug 19, 2024):
That specific error message looks like an issue with configuring the YubiKey settings.
Validate the these settings, restart and test again.
669b9db758/.env.template (L432-L438)@BlackDex commented on GitHub (Aug 19, 2024):
Or, your Vaultwarden is not able to connect to the Yubi Server.
Check your
/admin/diagnosticspage for details.@turnah commented on GitHub (Aug 19, 2024):
I've regenerated the yubi key, updated the confid and can log into my webvault with the new (as i could the old) but same issue on beta app.
digagnostics all look green, here is the support string:
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
@turnah commented on GitHub (Aug 19, 2024):
I've also run tcp flow with a authentication app key, as it fails on the app with the same message:
@tyde7 commented on GitHub (Aug 19, 2024):
same problem after update to 2024.8.0, except I cannot remove yubikey from 2FA. it shows
YUBICO_CLIENT_IDorYUBICO_SECRET_KEYenvironment variable is not set. Yubikey OTP Disabled. (I don't remember how I added it in 2FA in the first place...)@BlackDex commented on GitHub (Aug 19, 2024):
@turnah small warning, you did disclosed your email address, vault domain etc.. by sharing the last post.
I redacted the info, but that you know that at least.
@BlackDex commented on GitHub (Aug 19, 2024):
@tyde7 Are you using Cloudflare as well?
As I'm not able to reproduce this at all in any way. Also, you can remove all 2FA options via the Vaultwarden Admin
/admininterface.Also @turnah, the last post, if that really is what the client received, then it should have worked without any issue.
I'm using the exact same version of the Android app, and i can login just fine.
Please try to use the debug version from here https://github.com/bitwarden/android/actions/runs/10291080138
The
-qa.apkhas debug enabled and you should be able to see debug data viaadb logcat.EDIT: I updated the link to the exact same build as i have installed on my phone which is
2024.8.0 (18985).Not sure which version you are running right now?
@turnah commented on GitHub (Aug 19, 2024):
I spoiled/randomised all the tokens/keys/values; so hopefully OK! Really appreciate you doing that and your help.
@BlackDex commented on GitHub (Aug 19, 2024):
@turnah, nope, the JWT was still able to be decoded, though partially, but still useful info was in there.
Also, the
Auth-Emailcontained your base64 encoded mail address.@BlackDex commented on GitHub (Aug 19, 2024):
And, comparing the outputs, they do match exactly what i see during my tests. So the output of Vaultwarden should be valid, and something unsupported is being received by the client in some strange way.
So, we would need to see what the client receives, which is (if i remember correctly) doable via the
-qa.apkversion.@turnah commented on GitHub (Aug 19, 2024):
Lesson learned... hopefully this one is better
using logcat and the -qa version linked
@BlackDex commented on GitHub (Aug 19, 2024):
Strange, that output looks as it should. Are there any errors or warnings in that same output with a reason why it failed??
It looks just fine too me.
@turnah commented on GitHub (Aug 19, 2024):
I've run it again, this time using my local instance of vaultwarden (internal caddy that uses hosts on my router) so this doesn't use cloudflare to take that out of the equation.
Her are the 2 seconds of logs
@ManuVice commented on GitHub (Aug 19, 2024):
I have the exact same issue like you.
The problem only occurs on android old app and beta app.
I use Cloudflare and NPM.
I can reproduce the error on a public vaultwarden server vault.pwbox.de
Desktop app Windows and Linux and browser apps work fine with 2FA
@Webserve commented on GitHub (Aug 19, 2024):
The same error here. Just tried the new beta app. I'm using DUO
@BlackDex commented on GitHub (Aug 19, 2024):
Very strange. I'm just unable to reproduce this on my environment at all. The responses all look ok as far as i can see.
It is going to be very hard to fix this without me being able to reproduce this with an environment i can control.
@Webserve commented on GitHub (Aug 19, 2024):
Just updated to the latest version and its working now :O.
Dont know it was the restart or the update.
(Didn't knew there was a new version :-)
@BlackDex commented on GitHub (Aug 20, 2024):
@ManuVice, I am unable to reproduce this via pwbox either using Bitwarden Mobile Beta.
I'm not sure what issue you have, but this is just not reproducible for me in any way.
@ManuVice commented on GitHub (Aug 20, 2024):
Thank you 👍 I will debug my phone and post information if I find something.
@ManuVice commented on GitHub (Aug 20, 2024):
I have tried another phone. With 2024.7.1 2FA is working fine, 2024.8 (18985) same error on my own vault and at pwbox.
At Bitwarden.eu I can login with Mobile Beta 2024.8 (18985), but it never asks me to insert 2FA. It will immediately login after my Master-Password (tried it 5 times).
I have create a logcat, but I think its not a problem of Vaultwarden Logcat
@BlackDex commented on GitHub (Aug 21, 2024):
@ManuVice, I'm not seeing any output from the Bitwarden app. That will only happen when using the
-qa.apkfile.While it also doesn't provide any useful info for me btw, it does show the http requests and responses, but that is all.
No error's or backtraces or something like that.
@BlackDex commented on GitHub (Aug 21, 2024):
I have some strange issues my self when trying to check an other issue. I'm unable to use login with device.
Even thought the connection/response seems to be 100% identical to the Bitwarden server, except for some values of course since those need to be different.
I have no clue on how to tackle this any further.
If there are android developers in this community and able to get more details out of the Bitwarden Android app in some way, please help us :)
@nickdollimount commented on GitHub (Aug 21, 2024):
I'm also having this issue. Got a new Samsung Tab S9 FE and trying to log into the app. I've re-added all my webauthn keys but it fails with that error. Mine is also failing with that error when using email verification codes. Interestingly enough, possibly unrelated, I'm not able to use the 'Log in with device' option either; it errors with, "We were unable to process your request. Please try again or contact us.".
As a workaround, I've removed all the two step options just to get logged in and added them back.
@BlackDex commented on GitHub (Aug 21, 2024):
I just found the issue with
Login with device, it's because we return milliseconds instead of microseconds, and that seems to break the client.@nickdollimount, did adding them again solved all the issues with all the 2FA's?
@nickdollimount commented on GitHub (Aug 21, 2024):
Unfortunately not. I tried re-adding them first when I was initially troubleshooting. I then removed them all again after just to get logged in.
@BlackDex commented on GitHub (Aug 21, 2024):
That strange thing is, that some people have issues with a public system, and if i use that, i have no issues at all.
Not sure what could be wrong there or which response is causing the client to work for one, and not for the other.
@ManuVice commented on GitHub (Aug 21, 2024):
For me I remove 2FA, login with email and password and after that I re-add 2FA.
I have tested the last app versions. Last version which works for me with 2FA is 2024.7.2-beta (18910).
Logcat com.x8bit.bitwarden-qa.apk 2024.8.0
@BlackDex commented on GitHub (Aug 21, 2024):
@ManuVice, so even 2024.7.3-beta (18938) breaks for you? And 2024.7.2-beta (18910) does work right?
And which 2FA are you using? Is it just one 2FA? Are all 2FA's broken.
So, what i would like to know is this.
Which items break, which do not.
If using Webauthn, what kind of device are you using, does it has any more restrictions added to it?
@ManuVice commented on GitHub (Aug 21, 2024):
Yes
Only Authenticator App. I will try the 2. and 3. tommorow
@Gerardv514 commented on GitHub (Aug 22, 2024):
Which Authenticator app are you using?
@ManuVice commented on GitHub (Aug 22, 2024):
Aegis
@tyde7 commented on GitHub (Aug 22, 2024):
@BlackDex I'm not using cloudflare, just nginx deployed in a server. And I didn't find an option to disable 2FA completely. I could disable yubikey in admin panel but it doesn't help.
Is there anyway I could edit database and remove yubikey from it? I don' have yubikey, I might add a webauthn incorrectly to a yubikey. (I guess, not sure)
@BlackDex commented on GitHub (Aug 22, 2024):
@tyde7, that is only if you are adding a YubiKey as far as i know. That is nothing to do with WebAuthn.
If you want to use WebAuthn, you need to select that, and not YubiKey
I have a YubiKey 5C NFC, and that supports both YubiKey and WebAuthn.
You only need to have YubiKey settings for the backend to let it work.
You can remove all 2FA Options via the
/admininterface at the user overview. There is a link which does this.@ManuVice commented on GitHub (Aug 23, 2024):
I'am using Authenticator App with Aegis.
Error wrong pin
I could only test Authenticator App and E-Mail. To my surprise, email didn't work either... wrong pin.
I have tried them one at a time and both at the same time.
YubiKey, Duo and FIDO2 WebAuthn I cant test sorry.
I have checked my installation of vaultwarden, diagnostic in admin interface is fine and my mariadb is set correctly utf8mb4 and utf8mb4_unicode_ci, websocket works correctly.
@turnah commented on GitHub (Aug 23, 2024):
I got the same results, authenticator using authy and also tested using another vault warden session (codes matched).
Email and Yubikey failed for me. Tested all individually.
Can get in if disabled all 2FA.
@BlackDex commented on GitHub (Aug 23, 2024):
So just to be clear, you do get the window to select a specific 2FA option? And then you are able to provide a code and press the submit button within the client? But then you are denied access??
Please provide the Vaultwarden logs during these attempts.
@ManuVice commented on GitHub (Aug 23, 2024):
Thats correct
Newest Android App 2FA failed
2024.7.2 (18910) beta 2FA works
@BlackDex commented on GitHub (Aug 23, 2024):
The logs say it all is ok haha.
@BlackDex commented on GitHub (Aug 23, 2024):
And @ManuVice, you are 100% sure you are running the latest version of Vaultwarden?
@LekisS commented on GitHub (Aug 23, 2024):
Had the same issue, it's coming from the Android Bitwarden Beta App, not Vaultwarden : https://github.com/bitwarden/android/issues/3796
@ManuVice commented on GitHub (Aug 23, 2024):
Iam running 1.32.0 at Docker with image vaultwarden/server:latest-alpine
@BlackDex commented on GitHub (Aug 23, 2024):
Ok, then i actually need the full unedited response from the Vaultwarden server.
.
I would suggest to provide me that information and trust me to not abuse it, but i see no other way on fixing this.
To provide this in a secure way, send it directly to me via the Matrix Chat to
@blackdex:matrix.org.Or send an
I prefer the Matrix way btw.
There are multiple ways to get the output.
Install the Bitwarden-qa.apkas describe above, and fetch the output withadb logcata few example are also above.Use the browser, i think the response should still be the same and it might help.
You need to use the developer console, and make sure you login using the same 2FA method.
Via the developer console you can export the session as a HAR file, which i then can use to see what what send and received.
Some info on how to generate a HAR file can be found here: https://requestly.com/blog/how-to-generate-har-files-in-chrome-firefox-safari/
Without this info it will be very difficult to see what is going on here.
I really need the unredacted version of this.
@BlackDex commented on GitHub (Aug 23, 2024):
Also, an other method which might work is using
tcpflow. This works if Vaultwarden is accessed via a reverse proxy and you do not have the connection between Vaultwarden and the reverse proxy encrypted.On the host where you have Vaultwarden running execute the following.
Port 8080 here is the port where Vaultwarden is listening on, change that to the port you are running Vaultwarden on.
@ManuVice commented on GitHub (Aug 23, 2024):
I will wait for a result of this ticket. maybe it saves some livetime 😄
@BlackDex commented on GitHub (Aug 23, 2024):
Ah that saves me the troubleshooting too.
It would also explain why I'm not able to reproduce, since apparently not everybody is having issues.
@garfieldairlines commented on GitHub (Aug 23, 2024):
Hi I think I got the solution for you. If you got any of this in your caddyfile :
well, remove it and try again ?
@turnah commented on GitHub (Aug 23, 2024):
I removed it, but it didn't work for me unfortunately. Thanks for the suggestion though
@garfieldairlines commented on GitHub (Aug 23, 2024):
Crap, got the same issue, with Caddy too and that did the trick, try removing everything in the Caddyfile except the reverse_proxy part ?
@BrendanxP commented on GitHub (Aug 23, 2024):
I have had the same issue on the beta Android 2024.8 app for a few days now as well. Running Vaultwarden which I updated to the newest version about a week ago (1.32.0-059661be), I use CloudFlare and then Nginx. I noticed that the Windows 2024.8 app does NOT have the issue. Moreover, login through the web is fine, as is the Android app 2024.7.
I have 2FA via Yubikey, fingerprint or email.
@tyde7 commented on GitHub (Aug 31, 2024):
@BlackDex it's kinda not working.. I already remove 2fa in vaultwarden admin panel, but I could still see it in personal information in webpage. And still could not log in from android device... is it possible that I just edit
db.sqlite3file directly? I tried to dump it to sql but not find anything...@BlackDex commented on GitHub (Aug 31, 2024):
@tyde7 , no removing the 2FA via the admin interface should really remove it. That will remove the configuration at least.
It will not remove the options from the web-vault page of that is what you think.
When configured there will be a green v there to indicate it is configured.
So, if you still cannot login even with 2FA removed, then something else might be causing issues.
@tyde7 commented on GitHub (Aug 31, 2024):
@BlackDex thank you so much~~ It is solved after I upgrade to latest version of vaultwarden. maybe the version used is too low..
@halms commented on GitHub (Sep 4, 2024):
My (stable) iOS app has just updated to
2024.8.1and can since not access my Vaultwarden vault.I'm running
latest-alpineDocker image, which currently is1.32.0.Edit: Same error also appears with latest testing.
I get a generic
This version of the app works fine with an account on
bitwarden.comserver.Is this related? Shall I open a new issue? Can I help debugging?
@BlackDex commented on GitHub (Sep 4, 2024):
@halms Are you using 2FA? Have you tried to clear the app data and login then?
@halms commented on GitHub (Sep 4, 2024):
Yes, I am using 2FA.
I have confirmed this works in the web vault, though (same server, same device, same Yubikey).
Also, the same Yubikey works with a
bitwarden.comaccount.I have tried deleting/reinstalling the app (iOS does not provide other means to reset the app data) and the error remains.
Edit: Further testing
@tammenha commented on GitHub (Sep 5, 2024):
So i had the error message on the new iOS App as well, but somehow managed to fix it with the following steps:
2FA wasn't active for that account when the error occurred for me.
@halms commented on GitHub (Sep 5, 2024):
Okay, good news!
I've run some investigation (thanks @BlackDex for the guidance), and was able to fix my case.
The offenders are empty (
null) passwords in the password history of vault items.These appear to not be allowed by Bitwarden, but tolerated by Vaultwarden.
The key to finding this was exporting my vault from Vaultwarden and trying to import to Bitwarden, which failed with a descriptive error message.
The best way to find those is searching for
"password": nullin a.jsonexport of the vault.But offending are only the ones within
"passwordHistory", not the ones within"login".Deleting (don't forget to also delete from the Bin) and recreating those entries has made it work for me.
You cannot use the clone/duplicate feature though, since that appears to keep the password history.
I assume the team will fix this on Vaultwarden server soon.
Let's see if this is the only (remaining) wrong one.
The 2FA issue described in https://github.com/dani-garcia/vaultwarden/issues/4870#issuecomment-2329689825 has dissapeared by removing and re-adding 2FA and/or switching to the
vaultwarden/server:testing-alpineDocker image.@didyouexpectthat commented on GitHub (Sep 5, 2024):
I have 6 times where
"password": nullappear in my json, all underloginnotpasswordHistory. passwordHIstory itself isnullin most cases, but in some where there is password history, there is always a value on mine.My json file imported without error on bitwarden.com
@halms commented on GitHub (Sep 5, 2024):
And you are facing the
An error has occuredmessage after logging into the Vaultwarden server, but it works fine with the imported vault on bitwarden.com?If yes, then it's probably relevant to compare the results of the
/syncendpoint between the two servers for the same vault endpoint?@BlackDex commented on GitHub (Sep 5, 2024):
@didyouexpectthat If what @halms mentions in the post above is what you see, please try to follow the same steps as @halms did.
Hopefully this provides the items which have an issue, and you can provide us more details about this.
Else i would ask to follow the steps described here: https://github.com/dani-garcia/vaultwarden/issues/4870#issuecomment-2306749481 and provide me with the results of that.
@IIIdefconIII commented on GitHub (Sep 5, 2024):
I have the same issue, on Chrome the addon works but the Bitwarden app refude my login credentials
@Gerardv514 commented on GitHub (Sep 5, 2024):
Ok good we have someone else with the issue, did you see the comments above on what is needed regarding logs /more information to see why it’s not working for you? Try and provide more information to give more insight on why it’s happening.
@IIIdefconIII commented on GitHub (Sep 5, 2024):
i think its because cloudflares reverse proxy. I dit upload all stuff inm a new ticket so my comment can be removed here
@towade commented on GitHub (Sep 5, 2024):
The error also occurs for me with a freshly installed vault server with an empty vault an a fresh Bitwarden Installation on iOS
@BlackDex commented on GitHub (Sep 5, 2024):
Useless comments unless you provide some logs stating something went wrong. You might have configuration issues or something else.
@towade commented on GitHub (Sep 5, 2024):
I have exactly the same problem.
Except that both the server and the app are freshly installed.
@BlackDex commented on GitHub (Sep 5, 2024):
Sync looks like it works as expected.
It could be a multitude of other items in between.
Also, try the
testingtagged version of the containers and see if that solves your issue.It might as well be a reverse proxy, or anything else.
The login went fine, the sync went fine.
I just tested it with a new user account, empty vault, not orgs etc.. And that works just fine.
So something else strange is going one for you.
And then it will be the same as for all other users here. If you have an issue, please follow the directions https://github.com/dani-garcia/vaultwarden/issues/4870#issuecomment-2306749481 and provide the information to me.
@adinghub commented on GitHub (Sep 5, 2024):
Indeed, removing the password that was null and everything worked fine
@towade commented on GitHub (Sep 5, 2024):
install the testing tagged version solved my issue.
Big Thx!
@sebsgr commented on GitHub (Sep 5, 2024):
Testing Tag works fine in my environment with multiple organization, 2FA and traefik proxy.
Tested with iOS App 2024.8.1 (1052)
Thanks to all contributors
@ZHconsultores commented on GitHub (Sep 6, 2024):
In my case, I wasn't able to sync via the new iOS app. After applying every fix mentioned here without success, got it fixed by deleting all my "Sends"
@BlackDex commented on GitHub (Sep 6, 2024):
And you probably did not captured any output of a broken response i guess? So no way for us to easy check what is going on.
Any idea on which version of Vaultwarden those sends were created and if they were files or text and which options?
@ManuVice commented on GitHub (Sep 9, 2024):
tested right now latest bitwarden android app (2024.8.1-beta (19099)) and docker image testing-alpine with PR #4932
2FA login works. Thank you!
@IIIdefconIII commented on GitHub (Sep 9, 2024):
Does it now also works behind an reverse proxy system?
@ManuVice commented on GitHub (Sep 9, 2024):
I use a cloudflare tunnel and on my side nginx-proxy-manager. No problems so far
@IIIdefconIII commented on GitHub (Sep 9, 2024):
Okok does the tunnel also have 2fa on loading the page? Myne example does have MFA in front of all my applications so the vaultearden can't reach the API of vault to auth because cloudflare is the mitm
@ManuVice commented on GitHub (Sep 9, 2024):
Do you mean something like Authentik?
No, I dont use something like that
@sbhal commented on GitHub (Sep 9, 2024):
After removing
"password": null, don't forget to empty the Trash on the web console, as the Trash is client-specific and not synced. Emptying the Trash on one client alone is not sufficient.@turnah commented on GitHub (Sep 9, 2024):
Appreciate your help with this one - testing tag has fixed for me
@BlackDex commented on GitHub (Sep 10, 2024):
The
testingtagged images should resolve all these issues as the PR was merged today.@ghanjiboy commented on GitHub (Sep 10, 2024):
Thank you for fixing this issue. Do you have an idea when this change would be released? If its a while away or unknown, is the recommended approach to use the testing image that was generated today?
@BlackDex commented on GitHub (Sep 10, 2024):
I hope this fix is enough. If so releasing a new version shouldn't be that far away.
@gmcinalli commented on GitHub (Sep 19, 2024):
Hi @halms, this is teally strange, I'm on the
testingversion of Vaultwarden now, I exported the vault in JSON (not encrypted), I don't have anynullpassword in thepasswordHistoryentry, but still the new app doesn't work.@Gerardv514 commented on GitHub (Sep 19, 2024):
Sounds like it’s a different issue then. Can you provide more details of your setup? Details of your entries etc to find the “what else” could be leading to the issues.
@gmcinalli commented on GitHub (Sep 19, 2024):
@Gerardv514 Nevermind, I don't know how but after using the
testingimage for few days and now returning to the last official one, everything works normally in the new iOS app, push notifications, sync, everything.I don't know if the
testingserver when it started the first time did some cleaning of my vault.@Gerardv514 commented on GitHub (Sep 19, 2024):
Are you sure you were on testing? Meaning you physically confirmed via admin/diagnostic page and saw the testing version number?
@gmcinalli commented on GitHub (Sep 19, 2024):
@Gerardv514 Yes, I've completely rebuilt the container after changing the version on my compose file.
@deThommy commented on GitHub (Sep 26, 2024):
I just don't get it anymore. I'm self-hosted on vaultwarden 1.32.0. Cannot make Bitwarden iOS Apps work on iOS18 ("an error occurred"). Webvault, windows clients, browser extensions and MacOS Sonoma all are still working -- YET i just tried logging into several website using Passkey on my iOS18 devices and to my surprise it worked like it always has (even though I'm not even logged in with Bitwarden, but the Passkey-Pop up just works. Does that make sense? For me it doesnt
@Gerardv514 commented on GitHub (Sep 26, 2024):
What is your iOS client app version?
@deThommy commented on GitHub (Sep 26, 2024):
Latest version that came out 3 days ago: 2024.9.2
@tim-rohrer commented on GitHub (Sep 30, 2024):
Unfortunately, this doesn't appear to be working for me. I only had one password that was null, which was deleted from the vault and the trash bin.
I'll work later on updating the Vaultwarden image I'm using, but the iOS apps I'm using are 2024.9.2 (1106) from an iPad (18.0) and an iPhone (18.0).
@BlackDex commented on GitHub (Sep 30, 2024):
Use
testing, all others are not ok right now in some special cases@tim-rohrer commented on GitHub (Oct 5, 2024):
Finally got around to
testingand that did work.Any word on when the fix will be rolled into released versions?
@Gerardv514 commented on GitHub (Oct 5, 2024):
1.32.1 was just released yesterday.
@gergan commented on GitHub (Oct 6, 2024):
I'm still having problems with the iOS app. I did have some null passwords, but not in the passwordHistory. I have changed all of them - one was in the thrash, so I permanently deleted it, and now the export does not have any passwords with null in them. I uninstalled and installed the iOS app, but this did not help. I saw that I have some organizational passwords, which I have exported through the Vaultwarden-Web and they also don't have null passwords. So I'm not sure what's going on and what I could do in order to resolve the issue. And yes I have the newest container, so the fix didn't work for me. And Importing the export in my Bitwarden account worked without errors
@BlackDex commented on GitHub (Oct 6, 2024):
@gergan
I have no idea. Because we then need to know what the exact output is during the sync to see what potentially could be causing an issue.
If you want to help, please follow the instructions in the comment here (and the comment after that) https://github.com/dani-garcia/vaultwarden/issues/4870#issuecomment-2306749481
@gergan commented on GitHub (Oct 6, 2024):
I'll look how to export it later. It seems the problem is not the sync or the log-in, the app works just normally (it suggest and supplies passwords in Safari for example), but shows the error on the view-screen (where all the entries should be shown). Sync works just ok, It shows the folders in settings and so on. So it is some dumb validation or something like that, which hinders it to show its main screen.
@BlackDex commented on GitHub (Oct 6, 2024):
Also @gergan items with
password: nullare just fine, just not if they are in thepasswordHistory.password: nullmeans no password is configured for that item, and does not cause any issue with any client as far as i know.@BlackDex commented on GitHub (Oct 6, 2024):
Maybe you can share a screenshot on what you mean? Because I'm not really following what the current issue then is.
@Gerardv514 commented on GitHub (Oct 6, 2024):
You should also post a new issue since this thread is for sync and log in issues. In the new thread you need to provide more information and logs, and not just saying I’m having the same problem. There could be something totally different going on than what was addressed here and therefore on the technical side is not the same problem.
@gergan commented on GitHub (Oct 6, 2024):
I'll create a new one probably in the evening - but just to show what I mean. Here are some screenshots, for the problem I have. The App could sync, work generally - but the search and the main view show this error



@BlackDex commented on GitHub (Oct 6, 2024):
That could have everything to do with the sync which is returned, or maybe not, but what Vaultwarden returns, is what the client needs to parse and decrypt. If there is anything wrong or strange with the response, then this might be a result of this.
@florianmulatz commented on GitHub (Oct 8, 2024):
Hi Guys - just telling - since I've updated the vaultwarden-docker-container to 1.32.1 the issue disappeared