Greg-DB Dropbox Community Moderator

@"yyyhhh" As Здравко said, you'll need to implement the Dropbox Chooser as covered in the documentation.

@"Здравко" Thanks for the feedback and suggestion! I'll pass it along to the team.

Thanks for following up. I'm glad to hear you already sorted this out. Yes, that's correct, while the account_info.read scope is the default/required scope for user-linked app registrations, it is not technically required for authorizations. As you found, you do not need to request it when having users connect to your app;…

@"user44" Здравко is correct; the Dropbox API still does not offer a way to programmatically disconnect the user from the app entirely (as opposed to only revoking a particular token).

@"akirapix" Yes, as Здравко said, business accounts can be different; they may have a "team space". By default, API calls to the Dropbox API operate in the "member folder" of the connected account, not the "team space". That means that by default, the contents of the team space will not be found. You can configure API…

Yes, you can use copy references if you'd like. Alternatively, you should also be able to use CopyV2Async as an admin from one team folder and specify the destination in the other team folder in the toPath using the format "ns:12345/copyname" where 12345 is the team folder ID of the destination team folder.

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

You don't need to switch to listing all of the namespaces unless your use case requires it. Team folders are just one type of namespace, so your scenario is effectively a subset of that example. The namespace ID for a team folder is the team folder ID, so you can get the team folder's namespace ID from the…

When using the .NET SDK, using the TeamFolderListAsync method is the right way to begin listing all of the team folders for a team. Be sure to also implement TeamFolderListContinueAsync as well though, to make sure you get the whole list. And then for any given team folder (or any folder), using ListFolderAsync and…

This should be fixed now. Thanks again for the report!

This should be fixed now. Thanks again for the report!

@"SC_dev4" Здравко is correct; this doesn't indicate a scopes issue. This indicates that your app doesn't have permission to use that template. Note that user file property templates are app-user pair specific. You can't use an access token for one app to access a template that was created with a different app. You…

Thanks for following up. I'm glad to hear you got that working. For reference, both api.dropbox.com and api.dropboxapi.com are acceptable for this.

The https://www.dropbox.com/oauth2/authorize... URL you construct points to a web page where the user would choose whether or not to allow the app to access their account. That means the app should direct the user to that URL in their web browser. The app should not try to access the contents of that URL programmatically;…

There are a number of ways to use the functionality, depending on what you're trying to do, but the pathRoot field, if being used, should not be empty. In order to access the team space, for instance, you should use the root mode and use the root namespace ID for the connected account. To clarify, is something in…

Apps using the Dropbox API should continue using the same API methods/endpoints, such as filesListFolder and filesListFolderContinue, and the same properties such as path_lower or path_display, however you may need to make some changes, such as to start using the “Dropbox-API-Path-Root” header to make sure you're accessing…

Thanks for the report! I'll ask the team to add this to the types.

That team has deployed a fix to address this. Please let us know if you're still see any more instances of this now. (If so, please share samples of the 'X-Dropbox-Request-Id' response header values.) Thanks!

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