Account Switching#1720
Conversation
|
|
||
| public override Func<CancellationToken, Task<Stream>> Stream => GetStreamAsync; | ||
|
|
||
| private Task<Stream> GetStreamAsync(CancellationToken userToken = new CancellationToken()) |
There was a problem hiding this comment.
AFAIK we shouldn't directly instantiate CancellationToken objects, it should instead be provided by an external CancellationTokenSource instead.
There was a problem hiding this comment.
Good point, I'll add this to the list to fix (or better yet replace outright per your comment below)
| } | ||
| protected async Task<AvatarImageSource> GetAvatarImageSourceAsync(bool useCurrentActiveAccount = true) | ||
| { | ||
| return new AvatarImageSource(useCurrentActiveAccount ? await _stateService.GetEmailAsync() : null); |
There was a problem hiding this comment.
Performance wise, wondering if instead we should just have a round frame + label and just change the color / change initials.
There was a problem hiding this comment.
Agreed - this was one of the first things I did and tbh I don't remember what pushed me in this direction. Adding it to the list.
| private readonly HashSet<string> _migrateToPreferences = new HashSet<string> | ||
| { | ||
| Constants.EnvironmentUrlsKey, | ||
| "environmentUrls", |
There was a problem hiding this comment.
Out of curiosity, what's the reason behind removing that key / what's the difference for the new PreAuthEnvironmentUrlsKey ?
There was a problem hiding this comment.
The pre-auth URLs are what the app uses when there's no user/account context, otherwise the per-account URLs are used.
| { | ||
| public static class Constants | ||
| { | ||
| public const int MaxAccounts = 5; |
There was a problem hiding this comment.
Not arguing with the limit, just curious, do we have technical reasons to block this?
There was a problem hiding this comment.
Technical, no (the limit was a directive from early on). Reading/writing the State object could become an issue once a certain number of accounts are added, but I believe that number would have be pretty high.
|
|
||
| public ExtendedObservableCollection<AccountView> AccountViews { get; set; } | ||
|
|
||
| public StateService(IStorageService storageService, IStorageService secureStorageService) |
There was a problem hiding this comment.
Not relevant for this PR but just noticed this, @fedemkr for your IoC work you'll probably want to have a separate interface for secure storage or merging both classes into a single service with GetAsync + GetSecureAsync methods.
|
|
||
| namespace Bit.Core.Services | ||
| { | ||
| public class StateService : IStateService |
There was a problem hiding this comment.
We already talked about naming improvements but now looking a bit better into it, it's mixing a couple of concerns, could be 2-3 services instead.
AppDataService: All of the data access helper methods, building on top of the storage serviceAccountsStateService: everything elseAccountsViewManager: optional, separating service code from UI related updates.
* Account Switching (#1720) * Account switching * WIP * wip * wip * updates to send test logic * fixed Send tests * fixes for theme handling on account switching and re-adding existing account * switch fixes * fixes * fixes * cleanup * vault timeout fixes * account list status enhancements * logout fixes and token handling improvements * merge latest (#1727) * remove duplicate dependency * fix for initial login token storage paradox (#1730) * Fix avatar color update toolbar item issue on iOS for account switching (#1735) * Updated account switching menu UI (#1733) * updated account switching menu UI * additional changes * add key suffix to constant * GetFirstLetters method tweaks * Fix crash on account switching when logging out when having more than user at a time (#1740) * single account migration to multi-account on app update (#1741) * Account Switching Tap to dismiss (#1743) * Added tap to dismiss on the Account switching overlay and improved a bit the code * Fix account switching overlay background transparent on the proper place * Fixed transparent background and the shadow on the account switching overlay * Fix iOS top space on Account switching list overlay after modal (#1746) * Fix top space added to Account switching list overlay after closing modal * Fix top space added to Account switching list overlay after closing modal on lock, login and home views just in case we add modals in the future there as well * Usability: dismiss account list on certain events (#1748) * dismiss account list on certain events * use new FireAndForget method for back button logic * Create and use Account Switching overlay control (#1753) * Added Account switching overlay control and its own ViewModel and refactored accordingly * Fix account switching Accounts list binding update * Implemented dismiss account switching overlay when changing tabs and when selecting the same tab. Also updated the deprecated listener on CustomTabbedRenderer on Android (#1755) * Overriden Equals on AvatarImageSource so it doesn't get set multiple times when it's the same image thus producing blinking on tab chaged (#1756) * Usability improvements for logout on vault timeout (#1781) * accountswitching fixes (#1784) * Fix for invalid PIN lock state when switching accounts (#1792) * fix for pin lock flow * named tuple values and updated async * clear send service cache on account switch (#1796) * Global theme and account removal (#1793) * Global theme and account removal * remove redundant call to hide account list overlay * cleanup and additional tweaks * add try/catch to remove account dialog flow Co-authored-by: Federico Maccaroni <fedemkr@gmail.com>
Type of change
Objective
Added support for using multiple simultaneous accounts in the mobile client.
Code changes
UserServiceand the new gateway for all storage queries. While this started out as a 1:1 mirror of the version in jslib, it morphed into something slightly different to accommodate mobile environments by only storing the info necessary to decrypt each user's data and performing said decryption upon switching accounts, only keeping the current account data in cache. Practically speaking this means unlimited accounts, though the loading/saving of the account list (state) would likely start to suffer after a fashion (varies by device, maybe 40-60 accounts or so). That can be optimized further but I'm not sure it's necessary.StateServiceUserServicecogsince it's used in the toolbar now and differs from theSettingscog (in iOS; The same image with a different color is used in Android)5.0.0.22911.3.2for account switching list drop Shadow2.80.3for drawing Avatar imageStateServiceis used for all storage requests now, nearly everything was touched in order to point to the new service and uses a nearly identical pattern (via dedicated methods modeled after this new interface instead of generic storage requests that we had before).Screenshots
Testing requirements
Before you submit