Steve L. Helpful | Level 6

In the end I worked around the problem. I can't definitely say it was in our code but I am working on the assumtion it was.

Digging deeper, this only occurs if I invoke connect from deep in our view hierarchy and so is unlikely to be a general problem and quite possibly is application specific. I'll keep investigating.

What would be very helpful would be an atomic batchUploadFiles which created and returned share links for all of the URLs in the uploadFilesUrlsToCommitInfo dictionary (to use Obj-C terminology). This would simplify sharing a batch of files, reducing both latency and the number of requests needed. Consider this a feature…

I have no problems changing to use the accountID going forward, but it would be very helpful if there were a way to get the V1 userID (read-only) for those who have thousands of existing installs that use the Dropbox V1 userID as a primary key. As things stand there's no way to associate existing users with their data.

I guess you're hands are tied if Google has made the change. I'll investigate adjusting the browser chrome to better simulate the in-app web view.

By the way, the documentation at https://github.com/dropbox/dropbox-sdk-obj-c#handling-the-authorization-flow still refers to the in-app web view authentication flow.

Poking this thread back into life, is there a way in V2 to get the V1 userId?

Thanks Stephen. I plan to use it to detect if a background batch upload session has abnormally terminated for any reason (unlikely, but it can happen). If that occurs I can re-initiate the batch upload.

The asynchronous and non-deterministic nature of the API will make that (ahem) "interesting". One final question: do you know of any situation (apart from the app terminating) where the responseBlock in a fileRoutes batchUploadFiles API call will fail to run?

 Thanks Greg. The specific situation I'm trying to accommodate is where a user repeatedly changes a file (e.g. editing an online document or cropping a photo). Is it sufficient to just call fileRoutes batchUploadFiles repeatedly and the document at Dropbox reflects the last invocation? Or do I need to add logic to queue…

Thanks Greg, much appreciated. We haven't had an App Store rejection to date, hopefully that will continue. Again, thanks. I appreciate the quick response. Steve

Thanks Greg, that last link helps a lot. BTW, there's a typo in Migrating OAuth tokens from earlier SDKs, in the unsuccessfullyMigratedTokenData code. The format either has an extra %@ at the start or there is a missing argument. NSLog(@"%@DropboxUserID: %@, AccessToken: %@, AccessTokenSecret: %@, StoredAppKey: %@",…

Can you point us to an example of using this with the new 3.0 SDK changes mentioned in https://github.com/dropbox/dropbox-sdk-obj-c/releases/tag/3.0.0 ?

I'd definitely like to see Dropbox Comments viewing and posting via the Core API. Even if posting was limited to the file owner.