Please check this page before reporting a bug. We may already have a fix for it! If you want to report a site where Dashlane isn't working properly, please go to this page.
If you updated your iOS device and lost all your data in the Dashlane app, then this is a temporary bug we had with our iOS update. Make sure you do not delete the app as this will permanently delete your data. We are working on fixing this now and getting back your data as soon as possible.
If your PIN code is not being accepted on your iOS device, then you have this bug. It will be fixed soon. However, you can easily fix it by following these steps:
Once that done, your PIN code should work properly.
The Dashlane extension in Safari does not work for now if you have enabled Two-Factor Authentication's second option (i.e. ask a code “each time I log into Dashlane”). We apologize for the inconvenience. This is currently being worked on and will be addressed in a future update. Thank you very much for your patience! In the mean-time, you can still use the Dashlane Browser. Check how to use it on iPad or on iPhone.
If you're using Mac OS X 10.9.0, 10.9.1, 10.9.2 or 10.9.3, there is a small bug where Dashlane will not work on these versions. Please update your OS to the latest version (Mavericks 10.9.5), which is free. More here: Upgrade to OS X Mavericks. Free on the Mac App Store
Safari has just sent out an update and this might cause a problem with the Dashlane extension. The first time Safari 7.1 or Safari 6.2 is launched, it will disable all installed extensions, including Dashlane. You will need to re-install the Safari extension by doing the following:
If you originally downloaded Dashlane from the Mac App Store and now it's not working in your browsers, please try opening Dashlane and going to Dashlane > Install Browser Extensions. If you don't see a window asking you what browsers you want to install Dashlane on, then please try the following steps:
If it still does not work, please open the Console application (which is located in your Applications/Utilities folder on your hard drive) and check if there are any errors there. Then you can contact us here for more help with this.
If you get an error message saying "Your Dashlane Extension seems not to be installed" "Install Now or Never Ask Again" every time you open Dashlane or Chrome, then this is a temporary bug that we're looking into now. Clicking on "Never Ask" won't stop this pop-up from appearing.
We're looking into this now and it should be fixed in the next update! Your Dashlane extension should still be working properly in Chrome. If not, please check this page here.
If your phone started to talk to you after you enabled the keyboard in the Dashlane Android app, then this is a bug that was acknowledged in the Samsung developer forums, and is apparently fixed in new devices. However, old devices still have the issue and so you need to turn it off. Please follow these steps:
Text-To-Speech activates when I activate the accessibility service!
Samsung’s dev team is aware of the issue and is reportedly working to solve it. This bug occurs on any app using an accessibility service (such as Dashlane, Lightflow, Tasker, NoLED, …). In the case of our app, an accessibility service is used to access the screen for application login analysis. This is the main feature of our keyboard so we can’t do without. The fix shown below has been reported not to have any effect on other apps using TTS (such as Google Navigation).
Here is the full fix that has been reported to work on most Samsung devices:
If you’re experiencing the same issue on another phone, try this:
Please refer to this article to see how to install the Chrome extension from the Chrome Web Store on Windows and how to remove it:
If the Dashlane extension is installed but still does not work in Chrome, please also check this article:
Your problem on Fidelity may actually be caused by the way the site obfuscates the login, which breaks our save & credential mechanisms.
If you let Dashlane automatically save the content of Fidelity's login form, it will save the ****** that Fidelity adds to your user name in the login form — it is a script from the web site that automatically hides it for more privacy and security. The problem is that Dashlane thinks those ******* are part of your user name, and mistakenly tries to update your user name saved in Dashlane.
To make sure everything works, you will need here to manually check the credentials details of your Fidelity password in Dashlane, and make sure your user name does not contain these ******** symbols:
Finally, probably the most important important part: you need to make sure Dashlane NEVER replaces or saves the login again when you log in. Otherwise, it will mistakenly replace your user name (the correct one) by the truncated user name that has been hidden by Fidelity and which contains *******.
To do that, click on the Never for this website button when Dashlane asks you to save a credential.
Logins that have a login and password on the first page then a PIN number on the second page are out of scope at the moment. This is because Dashlane always wants to put a password on the second page. But there’s a work around:
Create a second login for that site, and call it PIN so you can tell it apart from the original one. Then put anything in the login field but put your PIN number in the “Password” field. Then, when you get to the second page, you can click in the field and choose your PIN login and Dashlane will fill in your PIN.
You need to open the details for your Delta.com password in Dashlane and then uncheck Always log me into the website.
Then, you need to go to this site via your browser and not by clicking on it from Dashlane. This is because the automatic login won’t work for this site.
If you go to the site from your browser (by typing in Delta.com in your browser), Dashlane will fill in the first two fields with your login info. Then the Last Name field will appear. You need to click in the Last Name field to fill this in and log in.