You can now use your Google account to sign up and log in to YNAB. This can be in addition to or instead of your email/password combo; both login methods will continue to work. Impress your friends by switching between the two with an air of nonchalance.
Improvements & Bug Fixes
- Register scrolling performance got a huge boost. And that’s an understatement.
- General performance improvement across the app (thanks to an upgrade to Ember v2.9).
- We tweaked the login and signup forms to play nicer with password managers.
- Imagine you’ve activated a filter on the accounts page (e.g. to show only transactions from “This Year”). If you then searched your transactions, we’d actually clear the filter so it wouldn’t interfere with the search results. Then if you cleared the search, we’d restore the previously active filter. And we did, for the most part. Except if you cleared the search term using the
<delete>key we wouldn’t restore your filter. Or if you used multiple search terms and tried to clear the search by clicking on the little X icon. So when I wrote “we’d restore the previously active filter,” maybe I was speaking more aspirationally. Regardless, however you choose to clear the search, we’ll restore any previously active filters.
- On some budgets, filtering by a date range other than “All Dates” wasn’t returning the proper results. Fixed.
- Closed tracking accounts will no longer appear in the spending report.
- Clicking on different Credit Card Payments categories was not updating the “last payment” section in the inspector. That’s fixed.
- We recently made a change to focus on the outflow field when pressing
<enter>on the memo field instead of saving the transaction. We’ve now reverted that change so pressing
<enter>saves the transaction. Also, pressing
<enter>on a selected transaction will activate edit mode, which sounds cooler than it probably is.
- Our messaging was slightly off after you confirmed an email address change. The change went through OK, but the copy we displayed didn’t exactly jibe. That’s fixed now.
- You can now pass in the pseudo-budget-id
'last-used'instead of an actual budget id, to specify the last-used budget. So instead of using something like
https://api.youneedabudget.com/budgets/52f01dec-ea69-4745-b607-cffa8e1599f7/months/current, you could simply use
https://api.youneedabudget.com/budgets/last-used/months/current. It’s especially convenient if you only ever work with one budget.
- If you specified a
category_idas an empty string (i.e.
""), we would return a
500error. Not particularly helpful. Now, we’ll return a
400error with a message indicating that “a valid UUID must be specified”. Use
nullif you don’t want to stipulate a
category_id. For example, for an uncategorized transaction you should specify
- OAuth refresh tokens can only be used once. If you obtain a new access token using a refresh token, you will be given a new refresh token that should then be used for the next refresh. We’ve clarified this in the docs.