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
My understanding of the current Xamarin.Auth implementation design is that one can store multiple accounts for a single serviceID.
Do I understand correctly for TinyAccountManager, that you can only store 1 account for a serviceId?
If so, would you consider supporting storing multiple accounts for a single serviceId?
This would imply separating out serviceId from the Account class, and having a FindAccountsForService method.
The text was updated successfully, but these errors were encountered:
I think multiple accounts is something more common to enterprise apps. For now, we're happy to be using a "only-one-account-at-a-time" strategy... but I have worked on apps that require maintaining multiple accounts concurrently.
From my side, this is not something that is a current requirement - just wanted to throw it out there, as I've worked on apps where it would be.
My understanding of the current Xamarin.Auth implementation design is that one can store multiple accounts for a single serviceID.
Do I understand correctly for TinyAccountManager, that you can only store 1 account for a serviceId?
If so, would you consider supporting storing multiple accounts for a single serviceId?
This would imply separating out serviceId from the Account class, and having a FindAccountsForService method.
The text was updated successfully, but these errors were encountered: