To make sure that transaction statuses on the home page are refreshed correctly and the sync time remains fast, we need to make use of the walletChanged event with some throttling.
Issue being fixed or feature implemented
WalletTransactionObserver is combined with WalletChangedObserver into a single class (we can move other observers in there in the future).
Observers are run in USER_THREAD instead of SAME_THREAD.
ThrottlingWalletChangeListener is not used anymore since throttling is up to observers using debounce.
Related PR's and Dependencies
Screenshots / Videos
How Has This Been Tested?
[ ] QA (Mobile Team)
Checklist:
[x] I have performed a self-review of my own code and added comments where necessary
[ ] I have added or updated relevant unit/integration/functional/e2e tests
To make sure that transaction statuses on the home page are refreshed correctly and the sync time remains fast, we need to make use of the
walletChangedevent with some throttling.Issue being fixed or feature implemented
WalletTransactionObserveris combined withWalletChangedObserverinto a single class (we can move other observers in there in the future).USER_THREADinstead ofSAME_THREAD.ThrottlingWalletChangeListeneris not used anymore since throttling is up to observers usingdebounce.Related PR's and Dependencies
Screenshots / Videos
How Has This Been Tested?
Checklist: