Web Release Notes: March 12, 2019

Release Notes

  • Some of you might not know this, but YNAB is great at importing transaction files downloaded from your bank. This is really helpful when your bank doesn’t support directly connecting to it, or the connection is having trouble. Now that we’re all on the same page, you should know that we improved the way we import dates and times for files that end in .ofx or .qfx. Now we take the time into account and not just the date, which means that your transactions are more likely to fall on the correct date when they’re imported.
  • When linking to your bank account, we could sometimes show a really cryptic error message that started with “Missing translation” and got worse from there. No more!
  • Sometimes, when we hit a snag while importing transactions from your bank, we will keep trying in the background, and all you have to do is wait a bit for things to catch up. But when that would happen, we would previously make it look all “doom and gloom” and put an error icon in your sidebar. Now we will correctly tell you that the syncing is merely “delayed”.
  • When importing from your bank, there was a rare scenario that could cause the same transaction to get imported twice. It was confusing, so we fixed it.
  • When importing from your bank, there was a rare scenario that could cause the same transaction to get imported twice. It was confusing, so we fixed it.
  • If you’re looking at your budgets list, you can now still  create a new budget directly from the menu in the upper left corner even though there is already a “create new budget” button in the list of budgets.
  • We made some improvements to the way we tell you about your goals.
    • Added “Started” month/year
    • Added the goal type in the title so that you know what kind of goal it is.
    • We dropped the “s” from “GOALS” because that “s” was silly.
    • P.S. Indented bullet lists are difficult to format.

API News (for you developers out there):

  • You can now use insecure redirect URIs for localhost (e.g. http://localhost:3000) with your OAuth Applications using the Authorization Code Grant Flow. Previously we’d require that you redirect to https://localhost:3000 for local testing, which required a lot of annoying hoop jumping and certificate management. Hat tip to @kordonme for the request!