RTS, API v2 only uses the new account ID format, so we recommend moving to that if you're using API v2. You can use the getAccount method to get account information, including the account ID, from API v2 in the Java SDK. You can continue using API v1 methods if necessary though.
My app has been around since before V2 ... I already have UID in the database.
I have already converted OSX, IOS to V2, developed the .NET APP.
All of those have access to UID.
Now you are recommending that I stay on V1 for android ?
Is this a long term stable identifier ?
API v1 isn't deprecated, so you can use it if you want, but we certainly recommend moving to API v2 when possible.
For API v2, you should use the account ID, which is stable. As part of migrating to API v2, you should get the account IDs. I.e., for any access token, call the getAccount method to get the corresponding account ID.
I have been inserted the UID in the Database for unique purpose. It is an integer value. As i will integrate the V2 what i will do.
User A : uid:123456
get the data from datatbase like as
Select * from User where uid=123456 - Is working fine.
User A : dbid:asd3-asdf ds
Only coming the dbid is not there uid. How to migrate. Already 1000 user have uid. How to change dbid.
Please give solution.
The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.Sound good? Let's get started.