You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
Do we need to keep in-memory storage for UI testing only? (we test against real account/data on iOS, very integration-y and heavy) = Yes, keep it and conditionally consider the environment
devinreams
changed the title
Use Sync-backed LoginStorage and Remove test data
Use Sync-backed LoginStorage and Remove test data for release/debug builds
Nov 12, 2018
Actually use the sync keys to get and store data locally and expose in app.
To access my saved logins, I want to safely log into my account and access the common list of entries, confident that my passwords are secure.
Acceptance criteria
Should track when a username/password are used locally onlyIncorporate remaining Login Storage methods from android-components #40 will implement touchRequires #22
The text was updated successfully, but these errors were encountered: