NumberFormatException: null - for additional_info.original_amount

[JohannesHome]

I'm getting a NumberFormatException when deserializing the TransactionsResponse response from /rest/accounts/${id}/transactions for some users.

AdditionalTransactionInfo expects BigDecimal. But the response I'm getting looks like this:

      "additional_info": {
        "compensation_amount": "6,10",
        "original_amount": "575,40"
      }

I assume this is a bug?

[berend]

Yes, that looks like a bug. Looks like a String to BigDecimal is missing.

[berend]

Sorry for the delay, debugging this revealed some differences from bank to bank while parsing this. Only solution we have so far is rolling back to sdk version 1.5.1

[berend]

Also the bug is not a missing cast from string to decimal, but the value containing a comma , instead of a dot .

[berend]

fixed with #44

[JohannesHome]

Hey @berend, sorry to say this but I just looked at #44 and that PR actually simply swallows now the values.

So the following:

        "compensation_amount": "6,10",
        "original_amount": "575,40"

results now in null values Instead of an exception.

[berend]

Thanks for the feedback, I will look into this!

[berend]

We have some internal dependencies for this bug here. Some of our bank connector return , instead of ., we are fixing this on the API side, not on the SDK. This should only affect a small number of banks.

I am leaving this open until this is completely fixed.