Closed WouterFlorijn closed 1 year ago
We are also getting this error. This error is suddenly new from yesterday, nothing changed in our code:
This needs to be merged/fixed ASAP, because our app is now not able to make payouts.
It won't be; bunq is not actively participating in this development at all. We've swapped to the PR commit, luckily we are phasing out the use of this API next week so we can hang on for 1 week and then finally rid ourselves of this "library" :)
@SamMousa Hmm, too bad. Are you planning/going to use the normal JSON api next week? Or switch to a different company/API?
Switching away from bank API in general towards voucher API for rewards (our use case).
Aha, nice! Unfortunately we cannot switch to vouchers, so I guess we'll have to deal with this. Let's hope that this gets "Ali Prio" 😂 (article)
This is clearly a bug in the code, but I have no idea why it wasn't triggered until today. I guess this part of the code was never reached?
I thought exactly the same. I've analyzed the headers that are passed to this function. Bunq (apparently) started communicating a Access-control-allow-origin
-header that triggers this codes. As this piece of code is in place to "correctly case the header name". They expect it to be Access-Control-Allow-Origin
I guess, although I don't understand why that is important.
Steps to reproduce:
ApiContext::create
What should happen:
What happens:
Traceback
SDK version and environment
Response id
Not relevant.
Extra info:
This is clearly a bug in the code, but I have no idea why it wasn't triggered until today. I guess this part of the code was never reached?
The relevant method:
As you can confirm from the code,
$match
will always be a string, whilevsprintf
only accepts an array as second argument.