Auto-confirm Fails if Just 1 of the Configured XMR Explorers is Offline

[suddenwhipvapor]

Description

Reporting on a user's behalf:
I'm aware of the changes with the node provider and I can confirm this issue exists regardless of which node is used (I have even tried it with a local node). The issue is with the app code, as I stated, which gives up the moment any 1 of the XMR explorers return an UNRELATED error (meaning the error is OTHER THAN that they couldn't find the referenced transaction).
I'm going through the logs, and I must say it would take me multiple hours to scrub the logs of the private data since it is interspersed throughout. Also, nothing in the logs shows the exact error that was shown to me in the UI, something to the effect of "auto confirm not possible for this transaction". I have the full logs from the moment the Buyer sent the XMR to me until the very end, when I manually clicked the Payment Received button after seeing 10+ confirmations and the UI error.

The logs do show that 2 our of my 4 configured XMR explorers were indeed showing the correct status of the transaction with the buyer's posted tx ID and key. But auto confirm was denied because the other 2 explorers were not reachable.

Version

latest

Steps to reproduce

Expected behaviour

Actual behaviour

Screenshots

Device or machine

Additional info

[pazza83]

@suddenwhipvapor do you know if this going to be fixed in the next release with the removal of the outdated nodes and the inclusion of your own?

[suddenwhipvapor]

@suddenwhipvapor do you know if this going to be fixed in the next release with the removal of the outdated nodes and the inclusion of your own?

not sure, I would expect this to be the case as long as all preconfigured xmr explorer nodes are online