NotificationFilterUrlUser.Create throws unexpected exception

[mbedeker]

Steps to reproduce:

When calling NotificationFilterUrlUser.Create there is a valid response, but because the method ends with ProcessForId(responseRaw), an exception is thrown, mainly because there is no Id in the root of the response.

What should happen:

not really sure.. it should at least not throw an exception

SDK version and environment

• Tested on 0.12.4
• Sandbox
• Production

[bluewalk]

Confirmed, experiencing the same issue. The notification filter however, is created.

[kdekok]

This is still an issue. responseobject is of type NotificationFilterUrl instead of Id. The SDK uses FIELD_ID contstant to unwrap the json and crashes there.

[janssen-io]

Is this SDK still maintained by Bunq? It seems absurd to me that this issue (together with #131) just don't get fixed in four years time.

Edit: from this comment on the PHP SDK project, I found out that we can use the NotificationFilterUrlUserInternal.CreateWithListResponse([]) (or NotificationFilterUrlMonetaryAccountInternal) to replace the list of the callback URLs.
However, these classes don't offer a replacement for the List operation. So not sure what's the best way to append a callback URL at the moment.

[bluewalk]

@janssen-io it indeed seems that bunq has stopped maintaining this SDK although the bot keeps regenerating the code...

[two-trick-pony-NL]

👋 Hey @mbedeker

I work at bunq and am currently reviewing the bunq API docs, open issues and SDK’s and came across your issue. I know it’s been open for a while, and I’d love to understand how it’s impacting you. Beyond the obvious -fixing this issue-, what else could we do to improve your experience with our API?

If you want to share your thoughts on how we can improve on our public API:

📅 I'd love to schedule a 15 minute interview to understand your needs through: Calendly
💬 Or if you don't have time for a call, you can give us some general feedback through this form

Your feedback will go straight to our product team! 🚀

[two-trick-pony-NL]

Hi! We're closing this issue as it's tied to an older version of our SDKs, and we've since completely revamped them as part of bunq Update 28.

This is a fresh start—we've tested the new SDKs extensively, and we’ll be putting them to the test again during our upcoming hackathon this Friday, where we’ll fix idiosyncrasies on the spot. (You’re welcome to join us!)

If this issue (or a new one) shows up with the updated SDKs, feel free to reopen or file a new report—we're happy to jump on it.