Greg-DB Dropbox Community Moderator

@"VijayKumar E" As Здравко said, if the path values are not set, that indicates that the item is not currently mounted under that account/root. For sharing information, you can check the 'sharing_info' field which would be set if the item is in a shared folder. Check out the documentation for /2/files/search_v2 for more…

You can find the information for any particular field/value for the Dropbox API in the documentation. For example, it sounds like you're referring to the 'id' and 'rev' values, such as in the FileMetadata type as returned by /2/files/get_metadata, for instance. In the documentation there, the 'id' field value is specified…

This is now available out of beta. More information can be found here in this new announcement.

@"Carpetes" As Здравко noted, from your code it does look like you are not building valid JSON. For instance, it looks like you're missing a quote and a comma after the $TargetFilePath in your $arg. Make sure you're building valid JSON when making these calls. For this reason, we generally suggest using some JSON library…

Is this the exact code you're running? I just tried this code myself and it worked successfully for me. When I plugged in an access token, it printed out the account information and did not throw that error. The getCurrentAccount method is implemented here.

@"fbx_dsb" The Dropbox API doesn't offer access to that "Recents" information, 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 looks like the file wasn't directly shared to you specifically (e.g., it may have been accessed by a link instead),…

@"user44" As Здравко said, you can use the getTemporaryUploadLink, upload, and/or uploadSessionStart functionality to upload files. Likewise, for downloading, there's the getTemporaryLink and download functionality. As for how to call such methods with DbxClientV2, check out the examples in the readme and in the examples…

Apologies for the confusion. The Dropbox API is officially supported, and you can find the support resources for it on this page. As for the issue you're seeing, I understand that you are attempting to list all files/folders using /2/files/list_folder. Note that this functionality is paginated and you are not guaranteed to…

For items like that which can't be downloaded using /2/files/download, you should use /2/files/export instead. I'll bring this up with the team to see if they're ready to remove the "preview" label for that endpoint.

@"Adi4" Здравко is correct; Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information on this migration here. Apps can still get long-term access by…

This should be working properly again now. Please let us know if you're still seeing this issue. Thanks!

Thanks for the report! We're looking into it.

@"tuiren" Thanks for the feedback! I'll pass this along to the team.

Thanks for following up. If you can collect some more details from the affected users, that may be helpful. For instance, it may be helpful to know: * do the failures occur a specific amount of time? (as that may indicate a specific timeout) * are they using a particular browser? * are they in a particular region or using…

I don't believe we have a full example for that exactly, but I have a post here that may be helpful.

The Dropbox .NET SDK examples happen to use a listener, but the authorization flow itself also supports custom URL schemes when using PKCE. In any case, the Dropbox .NET SDK is not built for or tested with Xamarin/Maui/iOS in particular. I'll pass this along as a feature request for official support for that, but I can't…

This is the expected behavior; the team_data.member scope has a dependency on the team_data.governance.write scope so the team_data.governance.write scope is required if/when you enable the team_data.member scope.

I'm not aware of any changes that should be causing failures like that. Do you have any error/logging output to share regarding this issue? Also, how long do the connections run before they fail?

@"phunction" As Здравко said, you can omit the redirect URI entirely, in which case the user will be presented with the authorization code directly so they can manually copy/paste it into the app. Otherwise, to use a redirect URI if you can't use a server, you can use a redirect URI with a custom URL scheme for your app,…

It looks like you're sending the parameters as JSON, but the /oauth2/token endpoint expects them as application/x-www-form-urlencoded POST parameters, and so your parameters aren't getting read. Update your implementation to send application/x-www-form-urlencoded POST parameters instead.

Check the contents of the response body for that error response. It should contain a more specific error message.

[Cross-linking for reference: https://stackoverflow.com/questions/77624842/dropbox-webhooks-getting-team-related-response-instead-of-file-related-informati ] @"dhavalsoni" Based on the sample you shared, I see that your app is "team-linked", and so is receiving team webhook notifications. You can find the documentation for…

Unfortunately I can't promise if or when the scope information will be included in the public API responses.

@"jonokivex" Unfortunately I don't have a timeline to offer. I'll follow up here once I have any news on that.

Dropbox now returns "short-lived" access tokens, which automatically expire after a few hours. Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information…

Thanks for the report! That issue with using "rlkey" links in the Embedder is open with the team. I'll follow up here once I have an update on that. The Embedder does not offer an option for viewing nested images inside the Embedder instead of in a new tab, but I'll pass this along as a feature request. I can't promise if…

It looks like this is more about iOS and its interaction with local servers/Xamarin, as opposed to the Dropbox API itself. You may be better served by referring to resources about iOS or Xamarin for help with this. For instance, I found this thread which may be helpful.

Are you only seeing this reported by one customer? This issue doesn't reproduce for me, even when using the same request body sizes, and I'm not seeing any other reports of this error. I'm not aware of any issues on the Dropbox side that should be causing this. Is there anything on the customer's network connection, such…

Please open an API ticket so you can privately share the full response you're getting from that endpoint. We'll be happy to then use that to check on that for you specifically.

No, I don't have an update on this.