Locking on the Claiming TLM screen

[jpedro06]

Sometimes it crashes on the Claiming TLM screen due to wax.io not loading the transaction.

If you try to update the wax screen, alienworlds identifies it as a new transaction. I suggest adding a timeout for the wax, thus forcing the error in alienworlds and trying to repeat the process.

[anonieX]

Thanks, this will be worked on in the next version, the current focus is to support multiple resolutions.

[jpedro06]

Other errors on the same screen

• Encountered Error - Transaction's reference block
• Encountered Error - User started a new transaction

https://imgur.com/a/JK7DZBd

[filipmagula]

Regarding the issue in the first post - I had the same issue in Brave. Each 3rd to 5th claiming coused an error. I have switched to Chrome and now there is almost no issue. It get stuck sometimes e.g. once per two hours but no restart needed - just few manual clicks to make it running again for another 2 hours.

One more small advantage of Chrome is that there are no panels except the one dedicated to being controled by Selenium (connected with the another reported issue).

[anonieX]

Regarding the issue in the first post - I had the same issue in Brave. Each 3rd to 5th claiming coused an error. I have switched to Chrome and now there is almost no issue. It get stuck sometimes e.g. once per two hours but no restart needed - just few manual clicks to make it running again for another 2 hours.

One more small advantage of Chrome is that there are no panels except the one dedicated to being controled by Selenium (connected with the another reported issue).

I've also noticed that now, currently working on 1.2.1 for Chrome since that will be easier than the bar trouble with Brave. If enough people want Firefox added I can look into it.