Greg-DB Dropbox Community Moderator

Dropbox has multiple types of links for different pieces of functionality, such as "preview links" (/scl/fi) and "shared links" (/s). And yes, if you want to use the link options like "dl" or "raw" for direct access as covered here, you should use "shared links". You can create shared links using…

From your description and code, if you're uploading the exact same data again, the expected behavior in this case would not be to add another file. Note that uploading identical data to the same path results in no change. If you do want additional duplicate copies created, you can set 'strictConflict: true' and…

Dropbox doesn't offer a 'content_hash' or equivalent for entire folders, only files, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. If you want to verify an entire folder, you'd need to check each individual file in the folder you're interested in verifying.

@"af11" As Здравко indicated, it sounds like you're referring to the "welcome" definition in app.py in the mdwebhook project, which is used for the "/welcome" route. That route in particular is used as the "success_url" for the app in the app.json (for Heroku deploys).

@"thesongcompany" This thread was just referring to a warning message displayed in the console. That shouldn't have been related to any redirects. This is an old thread anyway though, so if something's not working as expected for you, please open a new thread with the details of the issues you're seeing, such as the…

When uploading files to Dropbox, you should just supply the raw binary data. In the code here, there are two things that look like they may be altering or affecting the format of the data you're sending: 1) 'base64: true' on your printToFileAsync method and 2) readAsStringAsync. Those methods aren't made by Dropbox though…

The Dropbox API doesn't currently offer access to the viewer history information that you can see on the Dropbox web site manually, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

Thanks for the report. There's a known issue causing that message to be shown unnecessarily. The team is looking into it. By the way, from that screenshot, it looks like your app currently processes the OAuth app authorization flow inside a web view, instead of the system browser. The OAuth app authorization flow should be…

To elaborate a bit on some of what Здравко was saying, note that in order to temporarily accommodate clients that don’t properly support automatically handling “Transfer-Encoding: chunked”, we’re temporarily rolling back that change, so that these links will no longer use “Transfer-Encoding: chunked” and will instead…

@"mbvistaprint" Is the lack of "Content-Length" specifically what is breaking your app? Earlier, based on the code and description you shared, you indicated it was the lack of a successful response at all. Please share a specific description of what exactly your app is expecting but not getting so we can advise…

The "X-Dropbox-Content-Length" header is not part of the HTTP spec and is not officially documented by Dropbox, so we can't recommend assuming that will always be present. I'm sending this along as a request to offer a guarantee on that, but I can't promise if that will be done.

Thanks for the additional context. I cannot provide support for third party clients unfortunately though, so please refer to the documentation/support resources for the client. Also, no, I can't offer a way to get help from the developers of the official Dropbox Android app itself. Apologies I can't be of more help in that…

@"mbvistaprint" Yes, there have been updates to our serving infrastructure but we need to make sure we understand exactly what the issue or requirement is to be able to help. Please let me know if your developers can identify the specific issue or need. Thanks!

@"mbvistaprint" Please note that using Postman may not accurately represent what your actual app itself is doing. For instance, it may be using a different version of HTTP itself (the Dropbox servers support both HTTP 1.1 and 2), etc. In any case, we can't provide support for Postman itself, so in case Postman is…

@"Здравко" Thanks. Just to clarify, I was referring to this portion in particular, which didn't indicate any of that: @"mbvistaprint" wrote: HEAD https://www.dropbox.com/s/6djz4es56yb5k1b/SelfExamCardInside.jpg?dl=1 15:02:27.057 Pretty Raw HEAD /s/6djz4es56yb5k1b/SelfExamCardInside.jpg Accept: */* cache-control: no-cache

Update: in order to temporarily accommodate clients that don’t properly support automatically handling “Transfer-Encoding: chunked”, we’re temporarily rolling back this change, so that these links will no longer use “Transfer-Encoding: chunked” and will instead return “Content-Length” on HTTP/1.1. We will begin rolling…

Update: in order to temporarily accommodate clients that don’t properly support automatically handling “Transfer-Encoding: chunked”, we’re temporarily rolling back this change, so that these links will no longer use “Transfer-Encoding: chunked” and will instead return “Content-Length” on HTTP/1.1. We will begin rolling…

Update: in order to temporarily accommodate clients that don’t properly support automatically handling “Transfer-Encoding: chunked”, we’re temporarily rolling back this change, so that these links will no longer use “Transfer-Encoding: chunked” and will instead return “Content-Length” on HTTP/1.1. We will begin rolling…

Update: in order to temporarily accommodate clients that don’t properly support automatically handling “Transfer-Encoding: chunked”, we’re temporarily rolling back this change, so that these links will no longer use “Transfer-Encoding: chunked” and will instead return “Content-Length” on HTTP/1.1. We will begin rolling…

Update: in order to temporarily accommodate clients that don’t properly support automatically handling “Transfer-Encoding: chunked”, we’re temporarily rolling back this change, so that these links will no longer use “Transfer-Encoding: chunked” and will instead return “Content-Length” on HTTP/1.1. We will begin rolling…

Update: in order to temporarily accommodate clients that don’t properly support automatically handling “Transfer-Encoding: chunked”, we’re temporarily rolling back this change, so that these links will no longer use “Transfer-Encoding: chunked” and will instead return “Content-Length” on HTTP/1.1. We will begin rolling…

@"mbvistaprint" You mentioned both "dl=0" and "dl=1". For clarity, which one are you actually using in your app? For reference, using "dl=0" would only give you the HTML preview page, not the actual file, so that's presumably not what you want. Using "dl=1" would give you the actual file, but would require the client…

This is related to updates to the Dropbox system that applies to new authorizations. This is something that needs to be supported by the third party app itself. Third party developers received advance notice of these updates so they could update their apps as needed, so please check if there are any updates to the third…

@"rdee" Thanks for the feedback. This was not pre-announced as this encoding type is a part of the HTTP spec itself, and is expected to be handled by HTTP clients automatically, but I'll share this with the team.

@"mbvistaprint" That does not appear to be a response from Dropbox itself. Can you share a sample value of the "url" variable that would be used in your code?

@"mbvistaprint" Thanks. In that case, can you share a sample? You should still be receiving a 200, though depending on the type the client may have to follow one or more redirects first (though that aspect shouldn't have changed).

@"mbvistaprint" Can you share a sample value of the "url" variable there for reference? (There are a few different types of links and options so I want to make sure I know exactly what you're using.) Also, based on this, if you're throwing that particular VcsValidationException exception at the bottom that would indicate…

@"saeeda" As Здравко mentioned, please make sure you're using the latest cursor each time, not just the original one. If something still isn't working as expected, please share the details, e.g., the steps to reproduce the issue and the code, so we can take a look. Also, can you clarify what you mean when you say "the…

@"Jeff B.63" As Здравко said, the API v2 Explorer is a good tool for building and understanding how to format Dropbox API v2 requests. You can also find specific information regarding each route in the API documentation. And yes, in addition to the portions you already mentioned, to make an API call like that you need to…

@"mbvistaprint" Thanks for the report. Can you clarify a bit around exactly how you're attempting to check the size? The thread Здравко linked to was more about the "Content-Type" than the length. Please share what kind of link you're using and exactly what value (e.g., what header(s)) you're reading so I can check on this…