This is just an initial attempt at making it clear which strings are translated and which are not. Non-translated values should stand out a bit more and also a developer should think about translations when adding new strings. These changes help support those two goals.
The root issue seemed to be, if a keyboard was shown for a focused EditTextView that was also disabled, older versions of android would crash inside the input manager which was impossible to catch with a try/catch block. The end result was major: some users could not restore their wallets. This work around addresses the problem by keeping the focused view enabled at all times. In theory this could result in some weird behavior but in practice, that's unlikely.
Allow a user to correct common errors by rewinding the chain and scanning again. We provide 3 options: quick - the shortest possible rescan that can occur, based on witnesses. full - rescan all the way back to the wallet's birthday. wipe - delete all sqlite database and begin again from the moment after the user entered their seed phrase.
The SDK now provides hooks for receiving a callback whenever a scan completes that includes information about the number of blocks scanned and duration. Use this info to report device metrics around scan speeds. This is in anticipation of greatly improving these numbers in the near future. Before that, we want to start collecting a baseline measurement.
This is one of the metrics that we want to collect internally at ECC over the term to see how user sentiment changes for the next several months as we work to add a lot of features and improvements.
The intention of this feature is to provide a way for adding the minimum viable implementation of t-addr support. Effectively, just enough to get transparent funds into the wallet's shielded pool. Robust management of UTXOs is and should be outside the scope of a shielded wallet.
Mainly involves using a network parameter rather than a separate build for testnet and mainnet. This network object is also now the source of the SAPLING_ACTIVATION_HEIGHT, which varies by network. The other major change is the way wallet initialization works, particularly around viewing keys. Under the hood, this involves a database migration so it is worth testing the upgrade path.
* New design for Wallet History
* History Row designed
Colour combinations used to design History row as per comment in same branch
Co-authored-by: Mandeep <bhalothiamandeep@gmail.com>
After looking at this more closely, it's clear that a refactor would help so that the view model drives the logic. However, that change is bigger than the scope of this work so I'll save it for an enhancement and just do this small change, instead.
Kevin Gorham
Eljo
Mandeep