Update: We pushed out second release today to fix a minor issue with one of our monitoring tools that helps us make sure everything is running like it should. This is a behind the scenes change so nothing visible should have changed.
So, today is the first regular release, in a while, that doesn’t have anything to do with our big project of switching YNABers over to our new direct import provider, Plaid. And much like an angsty teen in Seattle in the early 90’s, we’ve gone to Plaid. We’re now rad like Plaid. Whoa. How is this word not pronounced “played?” Turns out, that there’s no way to know. What is knowable, however, is what we’ve released today:
- Sorting by category wasn’t working as expected as of a couple of weeks ago. Categories were sorting by an internal ID instead of their names, which would explain why you kept overspending in your
- When converting a scheduled transfer transaction into a regular (non-scheduled) transfer transaction, running balances were incorrectly counting that transaction twice. If you saw this error, you are some kind of level 99 YNAB Red Mage or something. Converting a scheduled transfer transaction into a (non-scheduled) transfer transaction??? What even is happening there???
- If you had a popup (modal) open while you were editing a transaction and then you had clicked the date dropdown for the transaction, the app would crash. We fixed that.
- We’re asking Apple subscribers to confirm that they’ve canceled their subscription with Apple before going ahead to delete their YNAB account. Look, we think everyone needs a budget, but we also think that you probably don’t want to pay for an app that you’re planning on deleting.
The Public API now supports importing transactions on Linked accounts. When transactions are available from your bank, we allow you to click the “Import (10)” button on the web or tap “10+ New transactions to import, approve, or categorize” on mobile apps to bring these into your budget. Now you can perform this import from the API with a
POST to the