Greg-DB Dropbox Community Moderator

This should be fixed now. Please let us know if you're still seeing any issues.

The fix is rolling out and is not out fully everywhere yet.

A fix is being rolled out. Please note it will take some to fully deploy it.

A fix is being rolled out. Please note it will take some to fully deploy it.

A fix is being rolled out. Please note it will take some to fully deploy it.

I'm not sure what you mean when you say you are "not getting any type of response from the curl command". For reference, if you need to debug something with curl, you can use the "-v" flag to enable verbose mode. In any case, I haven't tested your new code, but the parameters look right. I also don't see where you retrieve…

@"rylincoln" Thanks for the note. I wasn't able to reproduce that exact behavior, but depending on how your device/browser was trying to play the video, it may have been automatically sending 'Range'. In any case, I'm glad to hear you're seeing it working again. We have begun to roll out a fix. Please note it will take…

@"rylincoln" In my testing, this issue is not affecting requests not specifying "Range" to the temporary links returned by /2/files/get_temporary_link; I am not seeing the incorrect "Content-Type" in that case. Note that some media/video players do automatically set "Range" themselves though. If you are seeing otherwise…

@"ak2k" The team is actively working to resolve this issue as soon as possible.

@"needo" The team is currently working on resolving this issue. We'll follow up once we have an update on this.

@"b3nZol" Thanks for the feedback! I'll share this with the team.

You can find information on how to encode parameters on download calls here: https://www.dropbox.com/developers/reference/json-encoding If that doesn't help, please share the steps/code to reproduce the issue, including a sample parameter value that causes it to fail, and whatever unexpected error/output you get so we can…

@"Jeff B.63" As Здравко noted, your request is not formatted properly. You can find information on how to call the endpoint in the documentation. The API v2 Explorer can also be useful for prototyping these calls; you can click "Show Code" to see how the call would be constructed in a few different clients.

@"WoisWoi" I don't have an ETA on a fix to share right now. I'll follow up here once I have any news.

@"Andruy2003" I don't have a timeline to share right now. I'll post here when I have an update.

@"athithan" Thanks for the context! I've brought this up with the team and I'll follow up here with any news on this.

Access tokens and refresh tokens are different objects and are not interchangeable, so you can't use a refresh token as an access token like that. Instead, whenever you need a new short-lived access token you should call /oauth2/token with grant_type=refresh_token and refresh_token set to the refresh token, like in step 5…

@"jowflores" I don't have an update on this yet. I'll post here once I do.

@"andrijaFlowNinja" This appears to be an issue on the Dropbox servers so we'll need to fix it on our side. We're working on it and I'll reply here once I have news.

Thanks, that's helpful. We're looking into it. I'll follow up here once I have an update on this.

It looks like you may be experiencing a new/different issue, so I've moved your posts here. Can you share the steps/code to reproduce the issue you're seeing, as well as any error or unexpected output you're getting? Thanks in advance!

Thanks for the report! We're looking into it. I'll follow up here once I have an update on this.

Thanks for the report! We're looking into it. I'll follow up here once I have an update on this.

Thanks for the report! We're looking into it. I'll follow up here once I have an update on this.

@"synology_support" This should be fixed now. Please let us know if you're still seeing any issues. Thanks!

In your JavaScript code, you're using the token as an access token, however in your .NET code, you're using the token as a refresh token. Access tokens and refresh tokens are different objects and are not interchangeable, so you can't use the same token both ways like that. If the token you have is a refresh token, you…

@"athithan" Thanks for the additional information. I'll ask the team to support "Dropbox-API-Select-Admin" on /2/sharing/list_file_members/continue, but I can't promise if or when that might be done though. Instead, you'd need to use "Dropbox-API-Select-User", but make sure you're providing the member ID of an account that…

@"athithan" To echo what Здравко said, how did you make these two calls? It may be helpful if you can share the request for each of them so we can take a look. Be sure to redact the access token though. You can open an API ticket here if you'd prefer to share privately.

I see you are requesting the refresh token, but you don't seem to actually be using it anywhere in the code you shared. Whenever you need a new short-lived access token, you should call /oauth2/token with grant_type=refresh_token, as shown in step 5 of the offline example in this post.

It is not possible to fully automate the OAuth process where the user chooses to authorize the app and the app then receives the resulting access token and optional refresh token. This needs to be done manually by the user at least once. If your app needs to maintain long-term access without the user manually…