-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to disable fetching of tx history on mobile network #9986
Labels
feature
feature requests
Comments
rasom
added a commit
that referenced
this issue
Jul 29, 2020
rasom
added a commit
that referenced
this issue
Jul 29, 2020
rasom
added a commit
that referenced
this issue
Jul 29, 2020
rasom
added a commit
that referenced
this issue
Jul 29, 2020
rasom
added a commit
that referenced
this issue
Jul 29, 2020
rasom
added a commit
that referenced
this issue
Jul 29, 2020
rasom
added a commit
that referenced
this issue
Jul 30, 2020
rasom
added a commit
that referenced
this issue
Jul 30, 2020
rasom
added a commit
that referenced
this issue
Aug 6, 2020
rasom
added a commit
that referenced
this issue
Aug 7, 2020
rasom
added a commit
that referenced
this issue
Aug 10, 2020
rasom
added a commit
that referenced
this issue
Aug 11, 2020
rasom
added a commit
that referenced
this issue
Aug 12, 2020
rasom
added a commit
that referenced
this issue
Aug 13, 2020
rasom
added a commit
that referenced
this issue
Aug 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow to disable fetching of tx history on mobile network
User Story
As a user, I want to have an option to disable fetching of tx history on mobile network to save mobile traffic.
Description
Currently we fetch history regardless of available network, and this might require some internet traffic (tens of megabytes on initial scan if account contains transactions and hundreds of megabytes if when listening to recent history during the day). This can be expansive for some users.
Acceptance Criteria
Notes
The text was updated successfully, but these errors were encountered: