Greg-DB Dropbox Community Moderator

You can get the user's space information using the API v2 Java SDK via DbxUserUsersRequests.getSpaceUsage: https://dropbox.github.io/dropbox-sdk-java/api-docs/v3.0.x/com/dropbox/core/v2/users/DbxUserUsersRequests.html#getSpaceUsage--

[Cross-linking for reference: https://stackoverflow.com/questions/43979979/cancellationtoken-in-dropbox-c-sharp-sdk ] The Dropbox API v2 .NET SDK doesn't support cancelling/cancellation tokens, but I'll be sure to pass this along as a feature request. 

No, I don't have an update on this right now unfortunately.

Due to a recent change in Google's policy around using OAuth flows in web views, we no longer support or recommend using web views to process the OAuth flow, in order to support users using "Google Sign In" to sign in to Dropbox. If you're developing with the Dropbox API on Android, we recommend using the official Dropbox…

[Cross-linking for reference: https://stackoverflow.com/questions/43965454/dropbox-api-how-to-access-the-app-folder-from-browser ] It looks like someone on StackOverflow was already able to help with this. Pete's answer there is correct, the app folder for an app that uses the "app folder" permission (and the "Apps" folder…

@"MarcoLI" I can't seem to reproduce this error. What version of the SDK do you have installed? In any case, a few things I noticed: - You don't need to redefine the Dropbox hosts. (Though, you have it commented it out anyway.) - You don't need to pass in the Dropbox hosts manually. You should just use the DbxClientV2…

I don't have an update on this on our side unfortunately. I'll check in with the team, and follow up here if/when I have any news.

[Cross-linking for reference: https://stackoverflow.com/questions/43917563/uploaded-files-are-not-in-dropbox ] Can you share the full output you're getting? Thanks in advance!

Dropbox doesn't offer any sort of SQLite interface. You'll need to download/upload the full updated file each time like any other file.

Thanks for checking in. I don't have an update on this yet unfortunately. I'll check in with the team, and ask them to document this.

Thanks for the detailed report! I'm not sure what the issue may be off hand. The team will look into it and we'll follow up here once we have an update for you.

As long as you're able to use it in Xamarin, using the Dropbox Java SDK is probably a better route. In that case, I highly recommend just using the pre-built Android app authorization flow. In that case, there should just be a few things you need to do: 1) Set up your manigest as shown here:…

@"Steve L.32" Thanks for the feedback. In the past, we've received requests to instead supply the SDK via a package manager, such as CocoaPods or Carthage. They require some setup, but it makes it easier to install updates to the SDK aftewards. I'll send this along as a request to offer the SDK as a standalone framework.

I'll be happy to follow up on this thread if/when I have an update on this.

No, I'm afraid I can't think of another workaround for this. Using the deprecated endpoint or using a placeholder file are the only things that come to mind. The shared links can't be "computed" exactly, since the token in the URL is randomly generated only when the link is created.

@"jade2" No, accessing a file via a shared link does not remove it from the owner's account.

That should technically work, but I don't recommend it, since it makes the process less obvious/more error prone. For instance, it may make it less obvious if the actual file upload failed, since the the file would appear to already be there as far as the user can see, if they don't check the file size. The user may then…

Thanks! We'll look into it.

The API doesn't currently expose this metadata, but I'll be sure to pass this along as a feature request. I don't have any information on if or when this might be added though unfortunately.

Can you share the code and output for these search queries? Thanks in advance! (By the way, note that there is an indexing delay on search, so wait a few minutes before testing a search for any new files.)

In general, you should use a redirect URI to redirect the user back to somewhere that your app can access the redirect URI with the parameters/fragment added to it. For a server-side app, that's generally just some route on the app's site. For a client-side app, that can be a custom local URL scheme. For example, the Java…

This is technically possible using the 'pending_upload' parameter on /2/sharing/create_shared_link, but that endpoint is deprecated. There isn't currently a non-deprecated way of getting a shared link for a pending file like this, but I'll be sure to pass this along as a feature request.

Thanks for the additional context!

The app authorization flow will be started whenever you call authorizeFromController. To prevent that from happening repeatedly, you should check if the user is already authorized before calling it. You can use authorizedClient to check that, as shown here:…

Please supply a TestFlight build as requested. Thank you.

I can't make any promises as to if or when that would be added, but I'm sending that along as a feature request.

The official documentation for the sharing routes for the latest version of SwiftyDropbox can be found be found here. The createSharedLink method was deprecated in favor of createSharedLinkWithSettings to match updates to the Dropbox product itself. If a link already exists, you can retrieve it using listSharedLinks.

Thanks for the additional information! If I understand correctly, you're using the API v2 .NET SDK, but you're trying to implement the app authorization flow the way the API v2 Java SDK does it. These two SDKs work differently though, so there will be a disconnect between the two. You won't be able to easily reconcile the…

The move method is an "RPC-style request", so you would use it like the samples in the documentation under "RPC-style request". Specifically, it would look like: [[client.filesRoutes move:@"/original_path" toPath:@"/new_path"] setResponseBlock:^(DBFILESMetadata *result, DBFILESRelocationError *routeError, DBRequestError…

Unfortunately, no, there's no update on this.