Greg-DB Dropbox Community Moderator

Como característica de seguridad de OAuth 2, los URI de redireccionamiento http:// no están permitidos. La mejor solución es usar un URI de redirección https://. Si no tiene un URI de redirección https:// para usar, una alternativa es no utilizar un URI de redireccionamiento en absoluto. Si omite el redirect_uri, el código…

Hi Mike, unfortunately this question sounds more like a general C# question about class and method structure and usage, which I'm afraid I can't offer help with, as it's out of scope for Dropbox API support and outside my area of expertise. Apologies I can't be of more help in that regard!

API v1 and API v2 should work the same way in this regard. You can use the same OAuth 2 access token from multiple instances of the same app, or you can create and use multiple different access tokens. Creating additional access tokens does not invalidate previous access tokens. If something isn't working as expected,…

Thanks for the context! I'll send this along to the team.

I believe there are some cases where Dropbox may already omit unnecessary events, but I don't have specific information on that available. (And if not, we indeed may want to make that optimization in the future.) Just make sure you're processing the entries as instructed in the list_folder documentation and you'll get an…

Hi Patrik, in general, yes, you can always re-use an old cursor, even if you've already received/used a newer cursor. (In some relatively rare cases cursors will no longer be valid, in which case you'll get the 'reset' error and need to start fresh from /list_folder, but that's not related to using newer cursors.) If your…

It looks like the issue is just how you're checking the .routeError case. Instead of this: case .routeError(let boxed, let requestId, nil, nil): do this: case .routeError(let boxed, _, _, let requestId): or more completely: case .routeError(let boxed, let userMessage, let errorSummary, let requestId):

For the 400 error, make sure you check the response body. It should contain a more useful error indicating the issue. The path value should be passed in JSON in the body (not in the URL itself) as shown in the example in the documentation:…

If you create a shared link to a folder, that link is specifically for the folder. However, that link does also enable access to the contents of that folder. If you attempt to create a shared link for a file or folder that already has a shared link, the call will fail with an error. You can catch that error though. I…

Thanks, since this is only occurring on some devices, there may be something device-specific, or specific to certain instances or versions of your app. Is there anything unusual about how your app is set up with respect to the Keychain? It sounds like perhaps the SDK isn't able to clear the access tokens from the keychain…

Apologies, I was misinformed in my last reply. The property groups aren't supposed to be returned in list_folder (they documentation only shows it because the FileMetadata type sample itself is re-used). The intent is that they would only be returned by get_metadata when specifying `include_property_templates`. The feature…

Based on that stack trace, this issue is occurring when you're calling "listFolder", because you're not supplying a valid "path" value. If you need help with that, please share the relevant code, including the "path" value you're supplying.

1. It sounds like you're referring to using the endpoints /2/sharing/list_folders[/continue] and /2/sharing/list_mountable_folders[/continue]. The /2/sharing/list_folders[/continue] endpoints will return shared folders you currently have in your account. The /2/sharing/list_mountable_folders[/continue] endpoints will…

Thanks for following up. I'm glad to hear you sorted this out.

Thanks! We'll work on debugging this with the build.

Thanks! You shouldn't have to do anything different depending on whether or not the official Dropbox app is installed. They should both use the same flow. For reference, does the Android sample app display the same issue for you? Also, I noticed you mentioned that code is in "onReturn". Did you mean "onResume"?

Thanks. That's actually the same version I've been testing on (albeit on Android 7.0.0). Your URL also looks correct, so we'll have to keep investigating. Some remaining things that would be useful: - whether or not this occurs with a non-Chrome browser - a sample build that reproduces the issue that we can try

@"mikemalter" No problem: 1. No, shared folders are not the same as shared links. There's a help center article that covers these two different kinds of sharing here: https://help.dropbox.com/files-folders/share-file-or-folder 2. Yes, you can call the API from essentially any platform where you can make arbitrary HTTPS…

No, it's not possible to customize these emails, but I'll pass this along as a feature request.

Thanks for the report. Calling DropboxClientsManager.unlinkClients() should remove the stored access tokens in the keychain and reset the stored authorizedClient, so what you're describing is unexpected. (Also, thanks for the note about the documentation. I'll ask the team to update that to correctly reflect…

Thanks for the post! Can you clarify what you mean when you say "the metadata of file or folder by such path then Dropbox returns nothing"? The Dropbox API is case-insensitive, so you should be able to query by path regardless of the case. If that's not working for you, please share the code you're using and the unexpected…

Hi Frank, I'll be happy to help here. "Question 1: Is this really the most efficient way that this can be done?" Reading through your description (thank you for the detailed write up, it really helps), I believe there are a few optimizations to make: a) "does a files.listFolder" ... "files.listFolderContinue" ... "then for…

The SwiftyDropbox SDK should already be compliant with Apple's rules. For example, it does already use SFSafariViewController on iOS. (Make sure you're using the latest version of SwiftyDropbox though, currently v4.2.1.) You mentioned that this is for macOS though. To my understanding, macOS does not offer…

Thanks! I see you're adding the template for the user, and then are listing the files for the user, but it seems you're missing the step of setting the values for that template for the desired file(s). That is, you're missing step 2 below: The basic flow would be like this: * Call…

Can you elaborate on what you mean when you say "no token is retrievable/available when control is passed back to the activity"? What piece of code isn't behaving as expected, and what does it do instead? For reference, to receive the token you should be calling Auth.getOAuth2Token as shown here:…

Thanks! We'll look into that error. And no, (as long as the authorization page URL starts with https://www.dropbox.com/1/connect as expected) that page should not have a redirect parameter. It's a special page for apps using the official SDK and knows about the db-<APP_KEY> URL schemes by default. Speaking of the URL, can…

@"mikemalter" It sounds like Dropbox shared links might be a good solution for your use case. They don't expire (though they can be manually revoked). You can create them programmatically using the API via /2/sharing/create_shared_link_with_settings (or a corresponding method if you're using an official SDK).

We don't currently have any plans for embeddable file requests, but I'll pass this along as a feature request.

Usar /2/files/get_metadata é a maneira correta de verificar se um item já existe. Se assim for, você receberá os metadados de volta. Se não conseguir um erro de `path/not_found`. --- Desculpe nossas traduções. Nossas traduções foram criadas usando um tradutor online. Nós gostaríamos de suportar todos os idiomas, mas…

Are you uploading the same data again? If the data is exactly the same as what already exists at the destination path, no conflict will occur and it won't create a renamed copy.