Greg-DB Dropbox Community Moderator

@"yyyhhh" Здравко is correct. You should use the Chooser as documented here, which doesn't support displaying the Chooser or login page in an iframe.

@"Pathirny" Rich is correct. Dropbox now issues short-lived access tokens, and for long-term access you should get a refresh token. In addition to the blog post Rich linked to, be sure to also refer to the OAuth Guide and authorization documentation.

Thanks for the note! The team is currently working on this. I'll follow up here once we have news on that.

@"Lukag" For more information, refer to the following resources: * https://developers.dropbox.com/oauth-guide * https://www.dropbox.com/developers/documentation/http/documentation#authorization * https://dropbox.tech/developers/using-oauth-2-0-with-offline-access

[Cross-linking for reference: https://stackoverflow.com/questions/78875640/access-dropbox-file-the-remote-server-returned-an-error-404-not-found ] Здравко is correct; be sure to refer to the documentation for information on how to properly construct these requests.

@"eni8ma" While connection issues are one way for a problem like this to occur, other constraints like I mentioned in my previous mentioned can also be the reason. I can only offer help on the Dropbox side of things though. So to clarify, are you getting any errors from Dropbox? You may need to debug/troubleshoot locally…

Dropbox does not have example code for directly calling the API endpoints from non-SDK .NET code. The Dropbox API documentation has examples shown using curl; you could use these as starting points and translate them to your .NET network client of choice.

While we can't provide support for .NET or Visual Studio in particular, as those aren't made by Dropbox, my understanding is that .NET Framework 4.6.2 supports .NET Standard 2.0, so I would expect that to work. I notice you mentioned you were using Visual Studio 2015 though, which is relatively old, and may contain issues…

@"eni8ma" From the information here, as Здравко said, it does sound like there is some local environmental problem, such as a connection issue, or perhaps a lack of resources/processing on the mobile device preventing it from continuously playing the video. You may also want to check the developer tools in the browser on…

@"SJ_Code" No, unfortunately I don't have an update on this.

@"yyyhhh" The Dropbox Chooser does not support taking an access token, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. As Здравко said, it instead just uses the current user's web session on www.dropbox.com.

@"Brad Henderson" Здравко is correct; these parameters should be sent as application/x-www-form-urlencoded, not JSON.

If you use the official Dropbox .NET SDK, you should use the latest version of it, which is currently v7.0.0 as shown in your message. That supports .NET Standard 2.0, so please make sure you're using that in your environment.

Thank you! We'll follow up here once we have any updates on this.

@"Simma" Can you reproduce the issue a few more times now please? We've improved some logging on our side which should help us investigate now. Thanks in advance!

Dropbox does offer an API you can use for listing, uploading, and downloading files, among other operations. You can find everything you need to get started with the Dropbox API, including documentation, tutorials, and SDKs here: https://www.dropbox.com/developers We recommend using an official SDK if possible, but it is…

Thanks! We're looking into it.

@"Simma" The team is looking into this, but has requested the value of the "folder" variable from the "dbx.files_download_zip_to_file(target, folder)" line that fails for reference. Can you please share that? Feel free to open an API ticket if you want to share privately. Thanks in advance!

The "refresh token is malformed" error would indicate that the value you're passing in to the "refresh_token" parameter does not have the right format. You would need to make sure you're passing in the full/exact value that you received in the "refresh_token" response field from /oauth2/token when you called with…

Thanks! We'll look into it and follow up here with any updates.

You can use batchUploadFiles if that works for your use case, and I'll ask the team to add documentation for that. You can find some usage of it in the tests here. The Java SDK doesn't have an equivalent unfortunately; I'll pass this along as a feature request but I can't promise if or when that might be implemented.

@"awb" This is still open with the relevant engineering team. I'll check in with them.

The Java SDK isn't inconsistent with the Swift SDK; it doesn't directly return a WriteError. The Java SDK uploadSessionFinishBatchV2 method returns UploadSessionFinishBatchResult which has an entries field which is a list of UploadSessionFinishBatchResultEntry each of which might be a failure, and if it is a failure it…

Thanks for the report! Can you share the full steps/code/parameter values to reproduce this error? Don't share any access token, refresh token, or app secret though.

The client_modified time can be set arbitrarily by the uploading client, so it can contain a significantly different datetime than server_modified. In particular, I believe the Dropbox desktop client takes the local modified time from the filesystem for client_modified when uploading the file. In this case, it seems that…

The uploadSessionStartBatch method doesn't actually have a route specific error type, because it doesn't have any route specific errors. (It's just Void.) You can see this in the uploadSessionStartBatch documentation where it says: Return Value Through the response callback, the caller will receive a <A…

@"Brad Henderson" In addition to what Здравко said, you may want to look at the documentation for the PostString method itself for information on how to use that. On the Dropbox side of things though, you can find the documentation for the Dropbox authorization endpoints here.

That private scope and corresponding private endpoint are not available for use by third party apps. Third party apps may only use the public endpoints, documented here.

@"gavinho" This is still open with engineering. I'll check in with them on this.

@"xavdid" As Mark noted, this may be something that the developer would need to address in the app's code. The Dropbox API should certainly still return old folders, but if it doesn't seem to be working as expected, the developer can share the relevant technical details so we can look into it.