Cannot buy BTC - Error message possiblePaymentAccounts.isEmpty()

[trigger67]

Description

I wanted to accept a buy order to purchase BTC with euro, with payment method SEPA(IT).
When clicking on the button I have a popup with an error message telling :
possiblePaymentAccounts.isEmpty()

Version

V1.2.3

Steps to reproduce

I just opened BSQ, went to "buy BTC" and clicked on "accept buy order"

Expected behaviour

The "payment process" should start

Actual behaviour

Popup with error, and then when I click again on the "accept buy order" button, nothing happens.

Screenshots

Device or machine

Classic computer with a i7 7700k on Windows.

Additional info

It is the first time I try to use my SEPA account. I created it some days ago.

bisq - Copie.log

[p7996619]

Seems like the fix is already merged (#3625), but I'm also waiting since 1.2.3 release for a new one, as it basically prevents me from taking any interesting offers.

[incogneatoe]

Description:
I am also having the same issue. When clicking on the "TAKE OFFER TO BUY BTC" button, there is a popup with an error message stating:
possiblePaymentAccounts.isEmpty()

Version:
V1.2.3

Steps to reproduce:
Open Bisq application, from top menu select "BUY BTC", and then click "TAKE OFFER TO BUY BTC"

Expected behavior:
The "payment process" should start.

Actual behavior:
Popup with error message stating "possiblePaymentAccounts.isEmpty()", and unable to proceed with the payment process. Then I exit back to the main "BUY BTC" page and attempt to click a different "TAKE OFFER TO BUY BTC" button, nothing happens with no error message, the page is stuck.

Device or machine
MacBook Pro MacOS 10.15.1, as well as, Toshiba PC laptop Windows 8.1

Additional info
Had a successful process the day prior, but since then, each attempt has had the same error message. Also, attempted this process on V1.2.2 and V1.2.3 with the same result.

[trigger67]

I downloaded the last version of the code (future 1.2.4) and was not able to reproduce it. It seems fixed to me.
@incogneatoe @ForteUnited could you try ? Maybe when 1.2.4 is out .

[trigger67]

I am closing the issue if OK for everyone ?

[ForteUnited]

I am closing the issue if OK for everyone ?

yes

[rafaelpac]

Yes, I fixed it in PR #3625, which was merged and is effective since 1.2.4.

[trigger67]

Fixed in v1.2.4