BofA Connection Error--Android

kathy234311

I've had a Bank of America Connectivity Error in my Android version of Quicken for at least a couple of weeks. It keeps offering "swipe to fix," and then wants my credentials. When they don't work, it says to try again or enter them at the website to make sure they're correct.

They ARE correct--I use them both in Quicken desktop and at the BofA website all the time. I tried logging in at the website, completed 2-step authentication, and then downloaded account transactions in Quicken (since logging in triggers a 10-min. requirement to do that) in case either of those was the problem, but Android still can't connect.

Any other ideas?

Quicken Anja

Hello @kathy234311,

Thank you for reaching out to the Community to tell us about your issue, though I apologize that you are experiencing this.

If you haven't already, I suggest resetting your cloud data from your Quicken desktop program and seeing if that may make a difference. However, before doing so, first, verify that the Dataset name and the File name match each other identically by navigating to Edit > Preferences > Quicken ID & Cloud Accounts (see below). 



If they do not match, please click Edit dataset name and change the Dataset name to match the File name exactly the same (do not copy the file extension: ".QDF"). 

Then, click OK in the preferences window and proceed to save a backup (just in case). From there, please follow the steps below to reset your cloud data.

1. Sign out of your Quicken Mobile app
2. On your desktop program go to Edit
3. Preferences...
4. Mobile & Web
5. Make sure sync shows it's ON and click on Reset your cloud data 
   
6. On the following screen you can leave the preselected option for "No, just reset my Cloud data", type Yes in the entry field to confirm, and click Reset
   
7. Wait for the sync reset to finish
8. Navigate to the Mobile & Web dropdown menu 
9. Select Cloud Sync to resync your data
10. Wait for it to finish syncing 
11. Sign back in on your Quicken Mobile app

Once that is done, see if the issue still persists.

Let us know how it goes!