if bunq doesn't manage to get this fixed tomo, ill get in touch with the owners of https://github.com/bunqcommunity so that we can make fork the bunq sdk and then better support it, If not ill just fork it in my personal account, either way, I think it will be quicker if we just fix it our selfs.
I happen to be one of the authors who worked on the official SDK 👍🏽
yes I'm also frustrated, so of course, with no offense to any employee or anything, I still want to be welcome to drop by the bunqer every now and then. There might be reasons why they could not have fixed this sooner. Unless I'm missing something, regeneration of the SDK code is needed nothing more, because a new endpoint has been released in the Pub API but there has not been a recent regeneration of the SDK's. So in other words, the SDK's are outdated. So let's just help them out by fixing it our self. If they don't manage to get it fixed soon. Not being able to use firefly-iii sucks.
Manual fixing it takes longer than just regenerating tho, but oh well.