After import, Gordian starts a rescan. The % meter holds at the first value. It says "Rescanning... 6%" and won't move. Manually refreshing the screen changes that fact: it'll update the %, until the rescanning is done and it denotes the amount of BTC in the wallet.
the swipe down however has to be firm and has to invoke the "loading accounts" message, which seems to be normal in iOS.
FN does not want to automate calls to nodes more then it’s absolutely required. Tor is slow commections can time out. You can use multiple nodes and multiple wallets. Imagine what happens if you want to talk to another node or wallet while that one is rescanning?
So it's good that the % meter only moves when the user explicitly requires it so by refreshing the screen.
My suggestion: change the message:
"Rescanning... 43% (refresh to update)"
(refresh to update) can be in much smaller caps than the Rescanning... 43%.
After import, Gordian starts a rescan. The % meter holds at the first value. It says "Rescanning... 6%" and won't move. Manually refreshing the screen changes that fact: it'll update the %, until the rescanning is done and it denotes the amount of BTC in the wallet.
the swipe down however has to be firm and has to invoke the "loading accounts" message, which seems to be normal in iOS.
FN does not want to automate calls to nodes more then it’s absolutely required. Tor is slow commections can time out. You can use multiple nodes and multiple wallets. Imagine what happens if you want to talk to another node or wallet while that one is rescanning?
So it's good that the % meter only moves when the user explicitly requires it so by refreshing the screen.
My suggestion: change the message:
"Rescanning... 43% (refresh to update)"
(refresh to update) can be in much smaller caps than the Rescanning... 43%.