Greg-DB Dropbox Community Moderator

@"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…

Thanks for following up. I can't offer any details on the implementation of the Dropbox Android app itself, but I'll follow up with any updates on the reports you linked to.

@"Diegovsky" Thanks for the feedback! For reference, not all of the functionality used in the Dropbox product itself is available via the API, but I'll pass this along to the team. In addition to Здравко's guidance, be sure to check out the File Access Guide and Detecting Changes Guide, if you haven't already.

Apologies for the delay; it appears your thread was only recently moved to this section of the forum. This error indicates that the app/user is being rate limited. The Dropbox API does have a rate limiting system, and if/when a particular connection might be rate limited depends on a number of factors, which can vary over…

It sounds like this may be because we recently updated the server back-end for some types of Dropbox links to use "Transfer-Encoding: chunked" (and accordingly not return the "Content-Length" response header) on HTTP/1.1. HTTP clients should automatically handle this, but it's possible yours doesn't. Are you able to…

Thanks for the report! We'll look into it.

Thanks for the report. I'll raise this with the team again. And yes, v5.0.0 was the last version before v5.1.0, where Java source and target compatibility was bumped to 11. The team applies updates to the SDK to the most recent version, but I'll pass this along as a request for support on older versions as well. I can't…

Здравко is correct, while the creation of new long-lived access tokens is now deprecated, we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we will of course announce that ahead of time.) That being the case, you can continue using existing long-lived access token(s) without…

That's correct, you'll need to check the list and filter based on the desired name. Shared folder names are not unique identifiers, so it's possible for there to be more than one for any particular name. That being the case, it's not possible to look up a specific single shared folder just based on a name. And yes, you…

Yes, as long as you implement the authorization flow as shown, the SwiftyDropbox SDK will automatically handle the refresh process for you in the background, without any further manual user interaction required. If something isn't working as expected, please show the steps you're following when seeing the issue and the…

By default, Dropbox API access tokens for your app(s) don't become invalid and yield 'invalid_access_token' by themselves, but there a number of different ways that a Dropbox API access token can become invalid, including:* the user or team admin can revoke all access tokens for an app by unlinking it on any of the…

You can find a working example of getting and using a refresh token to maintain long-term access with the .NET SDK here: https://github.com/dropbox/dropbox-sdk-dotnet/blob/main/dropbox-sdk-dotnet/Examples/OauthBasic/Program.cs That example shows how you can explicitly call RefreshAccessToken, but that's actually not…

The output here doesn't seem to mention any Dropbox code. Do you get any other error/output/stack containing any Dropbox SDK references? Also, can you elaborate on what you mean when you say you were "upgrading my code to the latest editions"? What specifically were you upgrading (for example, the Dropbox SDK itself, or…