We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
[SwiftyDropbox] Storing v2 accountId in DropboxAccessToken instead of v1 userId
Not really a critical issue, but for our project it brought some inconveniences. So, currently DropboxAccessToken stores user id from API v1, while Users.Account.accountId stores API v2 account id. ...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThanks for the writeup Aibek! I'm sending these along as feature requests, though I can't make any promises about if or when they'd be implemented.
One note, it doesn't sounds like you necessarily are, but just to be sure/for anyone else reading, you definitely shouldn't rely on email address as an account identifier in your app, as it can change on Dropbox's side. Either of the other account IDs (user ID or account ID) are better suited for that. Email is fine for display purposes though.
Hi Greg,
Are you saying that userID is sufficient to distinguish a unique Dropbox account? As our product were storing this information(userID) since V1, it is difficult for us to switch to another value(accountID) now unless we drop all our exisitng connected Dropbox accounts.
Thank you for the help.
Chao
- Greg-DB
Yes, both user ID and account ID uniquely identify Dropbox accounts.
By the way, you can call getCurrentAccount (or the equivalent method/endpoint in your platform) for each stored account to map from user ID to account ID.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
