adorsys/XS2A-Sandbox

ObaUI throws exception on Refresh transaction list

djole87 opened this issue · 5 comments

Hi,

It seems that there is a problem with ObaUI app.
Exception from http://localhost:4400/oba-proxy/api/v1/ais/transactions/-kNvXeX-S7kt_Q7egoiJYA/page?size=10&page=0&dateTo=2020-02-28&dateFrom=2020-01-04

Components used:
1.Ledgers v.2.9
2.XS2A v.5.10
3.ASPSP-Profile v.5.10
4.Consent-Management v.5.10
5.XS2A Connector-Examples v.5.10

image

Hi, can you please attach the Log message?

Here it is:

[ERROR][11:54:55.399] - de.adorsys.ledgers.oba.service.impl.service.AisServiceImpl: Failed to retrieve transactions for account: -kNvXeX-S7kt_Q7egoiJYA, code: 0, message: Error while extracting response for type [de.adorsys.ledgers.util.domain.CustomPageImpl<de.adorsys.ledgers.middleware.api.domain.account.TransactionTO>] and content type [application/json;charset=UTF-8]; nested exception is org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Unrecognized field "balanceAfterTransaction" (class de.adorsys.ledgers.middleware.api.domain.account.TransactionTO), not marked as ignorable; nested exception is com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "balanceAfterTransaction" (class de.adorsys.ledgers.middleware.api.domain.account.TransactionTO), not marked as ignorable (21 known properties: "endToEndId", "debtorName", "mandateId", "bookingDate", "purposeCode", "ultimateCreditor", "bankTransactionCode", "proprietaryBankTransactionCode", "creditorAccount", "creditorId", "amount", "transactionId", "valueDate", "checkId", "creditorName", "debtorAccount", "entryReference", "remittanceInformationStructured", "exchangeRate", "ultimateDebtor", "remittanceInformationUnstructured"]) xs2a-online-banking | at [Source: (ByteArrayInputStream); line: 1, column: 717] (through reference chain: de.adorsys.ledgers.util.domain.CustomPageImpl["content"]->java.util.ArrayList[0]->de.adorsys.ledgers.middleware.api.domain.account.TransactionTO["balanceAfterTransaction"])

We will fix this problem in the next release

Issue is fixed with the latest version! Will close it