Describe the bug
After a full restore, force-killing the app and relaunching causes order and dispute states to be lost. Orders show incorrect status in My Trades. But a manual refresh recovers them correctly.
This does not happen to users who have never performed a restore.
To Reproduce
- Perform a full restore on an account with active orders or disputes
- Confirm orders appear correctly after restore completes
- Force-kill the app
- Relaunch
- Orders show wrong state or are missing from My Trades
Expected behavior
Orders and disputes should show the correct state after relaunch, same as before the app was killed.
Smartphone
Additional context
-
Only triggers after restore. Those users who have never performed a restore can kill and relaunch the app without problems.
-
Related code: restore_manager.dart, _clearAll(), eventStorage, mostroStorage
-
A manual refresh or restore recovers the correct state
-
Documented in docs/architecture/DISPUTE_CHAT_RESTORE.md
Describe the bug
After a full restore, force-killing the app and relaunching causes order and dispute states to be lost. Orders show incorrect status in My Trades. But a manual refresh recovers them correctly.
This does not happen to users who have never performed a restore.
To Reproduce
Expected behavior
Orders and disputes should show the correct state after relaunch, same as before the app was killed.
Smartphone
Additional context
Only triggers after restore. Those users who have never performed a restore can kill and relaunch the app without problems.
Related code:
restore_manager.dart,_clearAll(),eventStorage,mostroStorageA manual refresh or restore recovers the correct state
Documented in
docs/architecture/DISPUTE_CHAT_RESTORE.md