Authorized Address and Authorized Mnemonic not autocompleting and freezing the IDE

[GuidoDipietro]

Hey, me again.

Another issue I've stumbled upon while using AlgoDEA is that sometimes (haven't been able to determine when, but it's almost always), if I select the Sender of a transaction using the "..." button, the Authorized Address and Authorized Mnemonic won't autocomplete - in fact, that dialog window will freeze and I'll have to kill my IDE (IntelliJ IDEA Community 2021.1 in my case).

Workaround:
Copy the address of the receiver and manually paste it in the "Sender Address" field, then change focus to another field. Doing that everything gets autocompleted alright and nothing freezes.

[satran004]

@GuidoDipietro Thanks for reporting this.

May I know which version of the plugin you are using?

I have seen similar issue in earlier version. There was a fix for this in one of the recent version

If it’s still there in 0.8.0, I will look into it.

[GuidoDipietro]

Hello. It's version 0.8.0 unfortunately.

Should you need anything else let me know 👍

[satran004]

Hello. It's version 0.8.0 unfortunately.

Should you need anything else let me know 👍

Thanks.

Are you using a local Algorand node (or Node in your local network) as target node ? If yes, can you please try with Algoexplorer testnet (https://api.testnet.algoexplorer.io) and check if the issue is still reproducible.

In previous version, I was able to reproduce this error only when my target node was a local Algorand server. (or, node in my local network)

I was never able to reproduce this error for a remote Algorand server like AlgoExplorer (https://api.testnet.algoexplorer.io)

Root cause : Local node was too fast to return the current balance of the sender which was causing UI freezing. So, after putting some delay, I have never faced that issue again. 5133444

But as the issue is still there, I need to check the root cause again.

[GuidoDipietro]

Hi.
I'm using a local Algorand node (Sandbox in modes release and testnet) when I face the issue.

Using the endpoint of the AlgoExplorer Testnet API the issue is not present anymore indeed.