I've been experiencing this right since I started writing integration tests for adex-mob - especially send/receive from one wallet to another on the same device (requires few re-logins back to back). Sometimes after you relog into different wallet it might be stuck on Loading..., sometimes it would be stuck on Loading... for a minute or two, and sometimes it is infinite, sometimes it would relog instantly, so it's basically like gambling for us.
Currently, I experimentally found the time after logout to let MM2 cool off a bit (this time differs for iOS and Android) so that next login would 100% succeed, right now this time is right after Log message that states that mm2 has dropped the current electrum thread. (about 2 min after logout)
We are at QA mainly interested in making our tests run as fast as possible so if there's any possibility to cut that time to seconds and not minutes, that would be a big boost.
I've been experiencing this right since I started writing integration tests for adex-mob - especially send/receive from one wallet to another on the same device (requires few re-logins back to back). Sometimes after you relog into different wallet it might be stuck on Loading..., sometimes it would be stuck on Loading... for a minute or two, and sometimes it is infinite, sometimes it would relog instantly, so it's basically like gambling for us.
Currently, I experimentally found the time after logout to let MM2 cool off a bit (this time differs for iOS and Android) so that next login would 100% succeed, right now this time is right after Log message that states that mm2 has dropped the current electrum thread. (about 2 min after logout)
We are at QA mainly interested in making our tests run as fast as possible so if there's any possibility to cut that time to seconds and not minutes, that would be a big boost.