I have a issue about dropbox api v2. Before I use db api v1, I used 2 api key (one for upload/download <DBSession>, one for sync data<DBAccountManager>) and run parallel. But when migrate to api v2, I only have a interface <DropboxClientManger>, so I just used a feature (upload/dowload or sync) in the same time. Anyone have any solutions for this issue?
Hi Greg K,
Sure. You can take a look my sample code below:
// Use for sync data
DBAccountManager *dbAccountManager = [[DBAccountManager alloc] initWithAppKey:dropboxSyncKey
// User for upload/download data
DBSession* dbSession = [[DBSession alloc] initWithAppKey:dropboxKey
You can imagine I have 2 buttons, one for login dropbox for upload data and one for sync data.
If you haven't clear yet. You can give a new question.
That's correct, the API v2 SDKs don't offer the exact same interface/functionality as the Sync SDKs did.
You can replicate that functionality though, using listFolderLongpoll. That enables low-latency notification of changes in the account.
Hi Greg K,
I have issue, please help me
Please image below :
As you saw, one folder I create normally and one folder is created by SyncAPI.
Problem: when I use dropbox api v2
[fileRoutes listFolder:kDropboxSyncFolder recursive:@(YES) includeMediaInfo:@(NO) includeDeleted:@(NO) includeHasExplicitSharedMembers:@(NO)]
Result: - with normal folder (above) response return only one folder
- with sync folder (below) reponse return all folder (include subfolders).
You have anyway can create a sync folder? because I need uniform for new app and older app.
Please help me
The first folder in your screenshot, without the puzzle piece icon, is a normal folder, (e.g., explicitly created by an app with the "full Dropbox" permission).
The second folder in your screenshot, with the puzzle piece icon, is a special "app folder", which automatically gets created when you connect an API app with the "app folder" permission to an account.
If you want to use the existing app folder, you can use the existing app key for your app with the "app folder" permission, in this case your "CaptureAudioSync" app. API v2 does support the app folder permission, so you can also use that in the API v2 SDKs as well.
Hi Greg K,
Yes, I undertood your idea. But as you knew, if my app used one key (key upload/download) and users logged in, then if I change appkey when user use feature sync data --> logging before will be closed session. :(
That mean, at same time my app can NOT use 2 features (upload & sync) :(
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.