toolkit-for-ynab: [BUG] Issues with latest version of YNAB

I’m still looking into the issues with Toolkit. Sorry it’s taking so long. Unfortunately there was a pretty big change here on YNAB’s side which has caused many issues. It’s not going to be a quick fix 😦

Release 3.0.0 is out. Went to 3.0.0 because we support the new extension manifest version but it looks like Firefox and Safari don’t support it fully. Either way, crashes should be gone!

Hey @joshmadewell,

Thanks for the update and for your work.
Please don’t be sorry, this is an open-source project, we all get this for free, of course, we can’t expect 24h support.

To appease people you could potentially disable temporarily the features that use this emberHook method, maybe with a small pop-up explaining it’s a WIP due to breaking changes on the YNAB side. But even that is not ‘expected’.

Take your time, and hopefully, there will be a fix soon, and if not, that’s how it is. Let’s all remember we are getting this for free, and that the people maintaining the project are doing this in their spare time.

Great project 😃

Yeah, there are about 30 or so features that all cause the same issue.

I’ve solved a bunch of them but still have quite a few left. Unfortunately, they all fail in different ways and basically require rethinking each broken feature so I don’t introduce bad performance issues.

It’s getting there. I’ve added a way to just “disable” features entirely which I’ll be doing for the heavier handed ones I just have time for right now.

@joshmadewell thanks for your help with getting this fixed!

Quick Question: Have you considered a Patreon page or something similar that would allow us to contribute financially to the maintenance of this product?

Hey y’all, I’m almost there! Hoping to find time today to finish this all off. Again, I will be temporarily disabling some features because I just don’t have the time right now to fix them but the toolkit will at least stop crashing YNAB.

That said, I do want to call attention that we do have a good relationship with the YNAB team. Though they did not notice/predict the changes they made would break the Toolkit, they have done so in the past and let us know!

My guess is that this change was pretty unsuspicious on their side and if they did the bare minimum of “load YNAB with the toolkit” I’m not sure they would have caught the issue.

The changes I’m making here should make us more resilient to YNAB changes but in the world of extensions this sort of thing is inevitable. I had definitely let the Toolkit take a backseat because of this exact problem. The more features we add, the more features we have to fix if this happens (this is why I’m looking for maintainers) but thankfully I’m still able to work on the project and get it fixed for y’all (even though the time I have is limited 🙁).

So I close with a big THANK YOU for all your support and a plead that we not take anything out on YNAB here, they’re engineers just like me and I promise they don’t want their users to have a bad experience just as much as me! That just happens to be their full time job 😄.

I am having the same issue. The same error popup occurs when I try to delete a transaction using the Edit menu. Disabling the toolkit allows it to work.

I always knew I loved the Tool Kit, but having to go without has made me realize just how efficient it makes keeping on top of the budget and how much I truly do love it. Thanks for creating it and thanks for working on a fix for the current YNAB upgrade. It is much appreciated!

I love this extension. That said, to play devil’s advocate, it is kind of annoying to be so dependent on an extension to make a product useful. Not that YNAB isn’t useful on its own, but it is frustrating that we end up relying on a third-party extension to an application for which we already pay $100/year.

Checking the console, it contains Toolkit Errors in the addToolkitEmberHook method (“Cannot convert undefined or null to object”), for the following features (I imagine it’s everywhere that gets called, so dependent on which features we’re using):

• BulkEditMemo
• ClearSelection
• RightClickToEdit
• ToggleAccountColumns
• DisplayTotalMonthlyGoals
• NotesAsMarkdown
• ToBeBudgetedWarning
• CategoryActivityCopy
• HideHelp

All look like the below (with different line numbers and function names, etc obviously)

  - Feature: BulkEditMemo
  - Feature Setting: true
  - Function: bound invoke
  - Message: Cannot convert undefined or null to object TypeError: Cannot convert undefined or null to object
    at Function.getPrototypeOf (<anonymous>)
    at addToolkitEmberHook (chrome-extension://ldhelmfcfdmaeondkcdgcnbhneihejgc/web-accessibles/ynab-toolkit.js:17135:31)
    at BulkEditMemo.addToolkitEmberHook (chrome-extension://ldhelmfcfdmaeondkcdgcnbhneihejgc/web-accessibles/ynab-toolkit.js:16951:76)
    at BulkEditMemo.invoke (chrome-extension://ldhelmfcfdmaeondkcdgcnbhneihejgc/web-accessibles/ynab-toolkit.js:17686:10)
    at chrome-extension://ldhelmfcfdmaeondkcdgcnbhneihejgc/web-accessibles/ynab-toolkit.js:16993:20
    at YNABToolkit.<anonymous> (chrome-extension://ldhelmfcfdmaeondkcdgcnbhneihejgc/web-accessibles/ynab-toolkit.js:14903:25)
    at Generator.next (<anonymous>)
    at fulfilled (chrome-extension://ldhelmfcfdmaeondkcdgcnbhneihejgc/web-accessibles/ynab-toolkit.js:14830:58)
    at p (https://ynab-evergreen-assets.youneedabudget.com/ynab-api-production/22.49/assets/ynab_web/assets/chunk.716f3e99de88abb68803.js:2:903617)
    at L (https://ynab-evergreen-assets.youneedabudget.com/ynab-api-production/22.49/assets/ynab_web/assets/chunk.716f3e99de88abb68803.js:2:905047)```

Just wanted to add my thanks for the incredible extension you’ve created, keeping us apprised of your (lightning-fast thus far) progress on the fix, and to second the notion that you should absolutely share a Patreon or some way for us to donate! Toolkit has been game-changing for me with so many different features. Please let us contribute to your beer fund! 🙏

Yeah, there are about 30 or so features that all cause the same issue.

I’ve solved a bunch of them but still have quite a few left. Unfortunately, they all fail in different ways and basically require rethinking each broken feature so I don’t introduce bad performance issues.

It’s getting there. I’ve added a way to just “disable” features entirely which I’ll be doing for the heavier handed ones I just have time for right now.

No worries, I was hoping this info might help troubleshooting but it seems to be much more involved.

I’ll add my thanks to the many others here. It is a brilliant add-on.

Just wanted to say Thank You for your prompt fixing of as many issues as you can. I know there’s still a way to go, but 3.0.0 is ‘usable’ and that’s enough for now.

It’s really amazing how much of my core YNAB experience is not due to YNAB at all, but YNAB Toolkit.

Do you have a Patreon or any such similar? If I’m paying YNAB every year I may as well send you a few bucks from time to time for the work you do 😃

Hi @joshmadewell. First, thank you for this extension, it’s been such a great addition to YNAB!

Second, to play devil’s advocate again, maybe the complexity of the extension might warrant a review of existing features and perhaps a poll to find out which are most and least used and possibly removing features to help simplify the code. Just a thought. 😃

Oh this has definitely been a topic of discussion before. We have so many features and I don’t even use 50% of them personally. The problem has always been “there might be someone using it” when it comes to removing features. I’ve certainly tried raising the bar of what sort of features can be added. Thing that are a one-off feature for one person’s specific use-case? Probably not going to be added. But if someone does the work to add a feature? I’ll typically let it in, it seems only fair and really, it’s not thaaaat big of a deal (as long as I understand what the feature is doing haha).

The real thing here is I’ve basically refused to add any sort of tracking so we can learn what features people are actually using. I don’t want to track data so…we don’t! It’s been a blessing because I don’t have to worry about tracking but a curse when it comes to “should I fix this or just delete it?” that comes up.

So…yeah we’ve thought about it but decided to just take on the burden instead haha.

Even if YNAB don’t want to hire Josh or implement the features officially, which can be argued is understandable, they could at least give Josh early access to major changes they’re going to make so he can prepare before the update goes public. Of course YNAB Toolkit is unofficial but it is obviously something a lot of people use. We pay 100$/yr for this experience.

I’ve worked for game company in the past and while we didn’t support mods officially, third party users started releasing modding tools anyways. While we didn’t have plans to officially support mods or hire these people, we gave early access to updates to the major mod maintainers and had them sign NDAs so they could be ready with their mod updates when the game update released. And this was for a game that costs 20€, not 100$/yr.

Thank you as well. I wrote to YNAB to at least ask them to inform Toolkit developers of significant changes. That costs them nearly nothing. Others could do so as well.

This is a good idea. YNAB is a great tool and while they don’t have anything to do with the open-source mods that are done, issues like this still reflect poorly on them.

Same issue! noooo I don’t want to use YNAB w/o the Toolkit!😃

https://www.reddit.com/r/ynab/comments/uw2d33/ynab_is_currently_down_for_maintenance/i9p2svs/

YNAB devs appear to be aware of this as well. I had the same issue as well in Brave and disabling Toolkit solved the issue.

Hi @joshmadewell. First, thank you for this extension, it’s been such a great addition to YNAB!

Second, to play devil’s advocate again, maybe the complexity of the extension might warrant a review of existing features and perhaps a poll to find out which are most and least used and possibly removing features to help simplify the code. Just a thought. 😃

@joshmadewell thanks for your help with getting this fixed!

Quick Question: Have you considered a Patreon page or something similar that would allow us to contribute financially to the maintenance of this product?

I 100% second this suggestion. Get used to the Toolkit extension and then try to live without it a few days, and I’m totally lost on basic functions. Sucks that the YNAB team doesn’t implement these features for what they charge for the product… and probably gain too much credit for functionality actually provided by the Toolkit. That said, it’s an awesome extension that probably keeps me using YNAB at this point and worthy of some $$'s support by all of us who feel the same.

If they care about their customers, it is easy to inform large projects that significant percentages of their user base depends on. It costs them nearly nothing to do so. Indeed, they should be thankful projects like this exist. I know I am.

How does it reflect poorly on YNAB?

Sent from Yahoo Mail for iPhone

On Tuesday, May 24, 2022, 12:53, ztoups @.***> wrote:

Thank you as well. I wrote to YNAB to at least ask them to inform Toolkit developers of significant changes. That costs them nearly nothing. Others could do so as well.

This is a good idea. YNAB is a great tool and while they don’t have anything to do with the open-source mods that are done, issues like this still reflect poorly on them.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

@joshmadewell Thank you for the update. Thank you very much for the work you put in this extension. It’s an important extension and if it was not available many people may not even use YNAB. We’re all going to have to be patient while this issue is worked out. I am also reminded on how much this extension does after I turn it off. Eye-opening.

Thank you as well. I wrote to YNAB to at least ask them to inform Toolkit developers of significant changes. That costs them nearly nothing. Others could do so as well.

@joshmadewell, Thank you for the update. It is appreciated. I also agree with @FlorianKempenich. Nothing is expected, it is free. Anything you can do, in whatever timeframe you are able to work on it is great!!! We appreciate your work. Thank you for everything you do!!

This is a pretty major issue. Is anyone working on a fix?

The author is aware of the problem.

Deactivating Quick Budget Switch worked for me on Chromebook Chrome.

Hi @joshmadewell. First, thank you for this extension, it’s been such a great addition to YNAB! Second, to play devil’s advocate again, maybe the complexity of the extension might warrant a review of existing features and perhaps a poll to find out which are most and least used and possibly removing features to help simplify the code. Just a thought. 😃

Oh this has definitely been a topic of discussion before. We have so many features and I don’t even use 50% of them personally. The problem has always been “there might be someone using it” when it comes to removing features. I’ve certainly tried raising the bar of what sort of features can be added. Thing that are a one-off feature for one person’s specific use-case? Probably not going to be added. But if someone does the work to add a feature? I’ll typically let it in, it seems only fair and really, it’s not thaaaat big of a deal (as long as I understand what the feature is doing haha).

The real thing here is I’ve basically refused to add any sort of tracking so we can learn what features people are actually using. I don’t want to track data so…we don’t! It’s been a blessing because I don’t have to worry about tracking but a curse when it comes to “should I fix this or just delete it?” that comes up.

So…yeah we’ve thought about it but decided to just take on the burden instead haha.

I agree on the idea of doing some sort of poll, or having a form to select yes or no on if you use a feature

This issue makes me wonder if anyone at YNAB ever uses this extension

They’re, it’s them who pointed me to the extension as a possible source of the issue I was reporting to them.

This issue makes me wonder if anyone at YNAB ever uses this extension. I can’t imagine they’d be unaware of the extension, in which case, given its popularity, I’d think the devs would at least have a simple test case for sanity checking their code changes with the extension prior to deploying such changes.

Agreed, it’s the only report I use when the Toolkit isn’t enabled.

Disabling the Toolkit really makes it glaringly obvious that YNAB standard reports are meh. I wish they would absorb this project into its ecosystem and make it the robust tool it has the potential to be.

They are indeed meh, though I do like the standard Spending report’s feature of being able to show a monthly Trends bar graph and even being able to click on a subcategory in the monthly trend bar graph view to get a similar trending view of a master category’s subcategories.

Disabling the Toolkit really makes it glaringly obvious that YNAB standard reports are meh. I wish they would absorb this project into its ecosystem and make it the robust tool it has the potential to be.

They probably spend the majority of resources on the training and marketing, not really on the product they want to keep as simple as possible, without features that might scare some.

That’s probably why we still have only one target per category and if you want to save for all your subscriptions over the course of the year, you have to calculate it in Excel, even though YNAB already has all those transactions on the scheduler. Imagine training for that functionality somebody whose math skills are challenged by the change in the shop.

On Thu, May 26, 2022, at 21:33, Ryan O. Hicks wrote:

I love this extension. That said, to play devil’s advocate, it is kind of annoying to be so dependent on an extension to make a product useful. Not that YNAB isn’t useful on its own, but it is frustrating that we end up relying on a third-party extension to an application for which we already pay $100/year.

I do agree as well. What’s interesting to me is why isn’t YNAB hiring or working together with Josh to implement some of these features that the community wants into their product as stable features to use? I imagine I’m not the only person that’s thought of this and I’m sure it’s on Josh’s mind too. Maybe it is on their roadmap to do some of these things but the tech debt I imagine is lofty among their teams as well. Hell, keeping all external accounts synced properly is probably a mini team within YNAB of its own.

— Reply to this email directly, view it on GitHub https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/2747#issuecomment-1138937565, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGT5KFOIKYJMLGAC5OW3SDVL7GZFANCNFSM5WWKTSEQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>

I love this extension. That said, to play devil’s advocate, it is kind of annoying to be so dependent on an extension to make a product useful. Not that YNAB isn’t useful on its own, but it is frustrating that we end up relying on a third-party extension to an application for which we already pay $100/year.

I do agree as well. What’s interesting to me is why isn’t YNAB hiring or working together with Josh to implement some of these features that the community wants into their product as stable features to use? I imagine I’m not the only person that’s thought of this and I’m sure it’s on Josh’s mind too. Maybe it is on their roadmap to do some of these things but the tech debt I imagine is lofty among their teams as well. Hell, keeping all external accounts synced properly is probably a mini team within YNAB of its own.

How does it reflect poorly on YNAB?

As shamadoo said, people are dependent on the toolkit. I know I am and I appreciate the effort people have put into the open source improvements. But, users may not necessarily be able to distinguish between YNAB dev and open source dev though. I am sure everyone on github understands the distinction, but that doesn’t mean that everyone using the toolkit does. I am sure YNAB has been getting a ton of support tickets about this.