Greg-DB Dropbox Community Moderator

Thanks for following up. In that case, please do please open an API ticket with the relevant app key(s) and webhook URI(s) so we can investigate this failure for you. We can also check our logs for see what happened with the email. Please make sure to open the ticket while signed in to the account that owns the app in…

Do you need to build from source for some reason, or would the pre-built package be fine? If you don't need to build from source, it would be easier to just use the pre-built package than to debug why the build is failing for you. For instance, you can replace this 'compile' line in examples/build.gradle with the…

The official Dropbox API v2 .NET SDK does implement certificate pinning. You can find information on that in the DropboxCertHelper documentation, and an example of using it here.

It sounds like you're probably using access tokens from the API v2 Explorer. That's just meant for prototyping calls, and is currently using early access to a new feature where it only returns short-lived access tokens. To get long-lived tokens, you should retrieve them for your own registered API app, instead of the API…

Whether or not you get certificate pinning automatically will depend on how you're calling the API. For example, some of the official Dropbox API SDKs certificate implement pinning for you. If you're not using one of the SDKs, you should refer to the documentation for whatever library you're using, if any. If you're…

Yes, you can certainly use the Dropbox API to upload and download files. That's our officially recommended and supported interface, and there are also some SDKs you can use to make that easier. As for the data format, that's up to you, but you could use a SQLite file, or a file containing JSON, or separate individual…

@"ags65" We looked into this, and it seems like you may be running in to this issue: https://www.raspberrypi.org/forums/viewtopic.php?t=223026 As noted there, you can try: To stop sending DFs, you can change net.ipv4.ip_no_pmtu_disc value to 1 in sysctl. I would also try reducing the MTU on the interface in order to…

The Dropbox desktop client does sync those particular extended attributes/Alternate Data Streams as listed in the help center article you linked to, but I can't recommend relying on those for syncing your own application's metadata with Dropbox. That's not meant as an official programmatic interface (like the Dropbox API…

@"bram_l" Thanks for the additional feedback! I'll pass this along as well.

Unfortunately I don't know what the issue may be here. We'll try to look into it, but I can't make any promises as it seems to be client-specific, based on the observation that it doesn't occur on your other computer.

There's no reason an upload without extra encoding like that should result in a corrupted file. If you can reproduce an issue where correct code and a valid original file results in a corrupted file when uploaded to Dropbox via the API, please share the steps and code to reproduce it so we can look into it.

I see you're adding a layer of base64 encoding via your call to base64_encode. You should not base64 encode the file data when uploading it. Try removing that base64_encode call.

It sounds like there may be a problem with how you're transmitting or encoding the data for the upload call. Can you share the problematic code?

Yes, when making an "RPC" style call, you don't use the "Dropbox-API-Arg" header, and your JSON should go in the request body, e.g., as set by 'CURLOPT_POSTFIELDS'.

[ Cross-linking for reference: https://stackoverflow.com/questions/60555529/how-to-get-url-of-images-hosted-in-dropbox-to-use-it-in-debug-mode-django ] From your Stack Overflow post, I see you're using the 'django-storages' project. We can't offer help with that project itself as it's made by a third party, so if you're…

There are a few different formats for Dropbox API v2 endpoints, documented here: https://www.dropbox.com/developers/documentation/http/documentation#formats For example, /2/files/get_metadata uses the "RPC" format, so it requires the parameters as JSON in the request body. Exactly how you set that will depend on your HTTPS…

Thanks, please let me know if you get any more error information. Also, https://www.dropbox.com/1/connect?... is just a web site and not something you would call programmatically. Anyway, at this point I don't have enough insight on the issue to say exactly it would work in some browsers and not others (and only on some…

Great, thanks for confirming that. All Dropbox API v2 endpoints (except OAuth endpoints) expect the parameters as JSON, though there are some different ways of sending them. You can find information about each one in the documentation. For example, the /2/files/create_folder_batch endpoint uses the "RPC" format, so it…

Unfortunately there isn't any extra debug option built into the SDK, and anything like that wouldn't really help in this case since the issue is happening in the browser itself. For browser issues, we would look for JavaScript error information, which you already provided in your original message. Nothing in that output…

Regarding your first question, yes, the "redirect_uri" value you specified on /oauth2/authorize should be the same "redirect_uri" value you then send to /oauth2/token. I'm not sure I understand your second question though. You can re-use your redirect URI for each authorization, but note that each particular authorization…

Is there a way for us to replicate that environment so we can reproduce the issue here?

It looks like you're just passing along a native object as the API call parameters, and curl is then applying the multi-part Content-Type. You should send up the parameters as JSON. You can build your parameters as JSON like: $params = json_encode(array( 'paths'=> $folders, 'autorename'=> false, 'force_async'=> false));

@"KenEm" You can find the information about this Dropbox feature here: https://help.dropbox.com/files-folders/share/set-link-permissions#disable-downloads

Thanks for the information. I just tried this on an Android emulator running API 22 with the built in browser (though it's reporting a different kind of version number: 5.1.1-552941) and that also worked for me. Do you have access to a device running a non-customized API 22? It would be useful to know if it does or doesn't…

@"marcoalt" We currently officially support three different installation methods for the Dropbox Objective-C SDK. Specifically: * CocoaPods * Carthage * Manual It sounds like you were initially trying to install it via CocoaPods, is that right? Can you double check you followed the instructions exactly as documented? Also,…

[ Cross-linking for reference: https://stackoverflow.com/questions/60534044/dropbox-saver-api-url-as-base64-works-when-upload-1-file-when-upload-multiple-i ] Using the Dropbox Saver with data URIs like this is unfortunately not officially supported, but we'll consider it a feature request.

From your screenshots, I see that your team is using the "team space" configuration. By default, API calls will operate only in your private member folder, and not in the team space, so you won't be able to access that "Sample Folder" outside your private member folder by default. You can configure your API calls to…

Thanks for the report! It sounds like there may be an incompatibility in some cases with Chrome. I just tried the Dropbox Java SDK's Android sample app as well though, and it worked for me, redirecting back to the sample app without issue. I just tried it with Chrome 80.0.3987.119 in particular. You mentioned you tried it…

Can you share the full /oauth2/authorize URL you used to get the authorization code you're exchanging, as well as the redirect URI you're sending with this /oauth2/token call (your 'url' variable in the above code)? Those need to match exactly. Keep in mind that you might have multiple different redirect URIs registered…

@"Андрей Г.2" I'm not quite sure I understand your question. Can you elaborate? Thanks in advance!