Greg-DB Dropbox Community Moderator

SharingFileLinkMetadata and SharingFolderLinkMetadata are each subtypes of SharingSharedLinkMetadata; they aren't three distinct types. So given a SharingSharedLinkMetadata, 'file' indicates a SharingFileLinkMetadata, and 'folder' indicates a SharingFolderLinkMetadata.

@"Sc0rp0w" App folders are incompatible with shared/team folders, meaning you can't share an app folder, put a shared/team folder inside an app folder or put an app folder in a shared/team folder. (The app folder name setting only allows you to set the default name of the app folder, not the full path, so you can't use…

@"TStack" Yes, refresh tokens do not expire automatically, so they can be used reliably for long periods of time, even years. Be aware though that refresh tokens/access tokens can be revoked on demand by the app or user.

@"TStack" Can you clarify what you mean by "sustainable"? 

@"TStack" If you're referring to any long-lived access tokens retrieved before the switch to short-lived access tokens and optional refresh tokens, note that while the creation of new long-lived access tokens is no longer available, we don't currently have a plan to disable existing long-lived access tokens. (If that…

Thanks for the feedback! I'll pass this along as a feature request, but I can't promise if or when it might be implemented.

This should be working now. Please let us know if you're still seeing any issues. Thanks for the report!

New update: The team has developed a new solution that should allow these requests with the extra new line to succeed. We've deployed this solution for all requests and expect to be able to keep it deployed permanently. Please note that we do still ask that you update your client code to avoid sending the extra new lines…

@"athithan" Can you try again and let me know if you're still seeing this issue now? Thanks!

Apologies for the delay in updating this thread. This error should no longer be occurring. Please let us know if you're still seeing any issues.

@"sisrael1" Yes, multiple concurrent uploads can trigger this lock contention error. Refer to the resources in my previous post for information on how to commit multiple changes in one call to avoid triggering lock contention with your own changes.

@"sisrael1" Also, note that if there are multiple changes at the same time in the same account or shared folder, you can run in to this 'too_many_write_operations' error in particular, which is "lock contention". That's not explicit rate limiting, but rather a result of how Dropbox works on the back-end. This is a…

@"munis-bto" No, I don't have an update on this request.

It looks like you're referring to the step where Dropbox redirects the user back to the URI you specify in the redirect_uri parameter you set on /oauth2/authorize. I just checked on this, and it does not appear Dropbox itself is removing the trailing "/" from that URL. I reproduced this, and looking at the log of the…

@"shsv382" Note that some error types are nested, so you'll need to expand the types to see the full information. To find the information for the "path" errors returned by /2/files/upload in the /2/files/upload documentation, for instance, start by expanding the documentation for "path" under "UploadError" in the…

@"shsv382" This issue was referring to getting a "path/insufficient_space" error when uploading a file, such as when calling the /2/files/upload endpoint. That kind of error would be sent with a 409 status code. You can find more information in the "Errors" documentation and Error Handling Guide.

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 requesting "offline" access…

A 'missing_scope' error indicates that while the app is permitted to use that scope, the particular access token you're using to make the API call does not have that scope granted. Also, be aware that just adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens or…

This is the expected behavior if attempting checkApp without an app secret; the checkApp method validates the app key and secret by calling /2/check/app which uses "App Authentication", which does require the app key and secret. So, that will fail without the app secret. If you want to check the validity of the access…

@"MogensBrun" qpo is correct; file IDs are case sensitive, and in some instances such as this, may vary only by case. So, make sure you're you're always preserving the case when storing these values, and using case-sensitive comparisons when comparing them.

The Dropbox API does have a general rate limiting system that applies to all account types, but we don't have specific rate numbers documented for that. Apps should be written to handle these rate limit responses automatically. Also note that not all responses with a 429 or 503 status code indicate explicit rate limiting,…

It sounds like you're referring to using the /2/files/get_metadata endpoint and setting 'include_media_info' to true, in order to get the media information such as 'dimensions' and 'duration' returned in the 'media_info' field in the result. That functionality is only available on /2/files/get_metadata, which does require…

I see our messages just crossed, but yes, it sounds like that's the issue. The access tokens can certainly be longer than 255 characters, and you may have only recently started receiving access tokens of that length, so a database limit like that would cause the issue. 

While not specific to results of automations, the Dropbox API does offer a few ways to detect when changes occur, such as when new files are added. For information, please refer to the Detecting Changes Guide.

It sounds like your database may be corrupting the access token, causing the subsequent API calls using the retrieved corrupted access tokens to fail. In particular, might your database have a length limit for storing the access tokens, which effectively truncates them? Note that Dropbox API access tokens can vary in…

Yes, you can use the Dropbox Chooser to have the end-user select any file or folder from their account to send a shared link for that item to your app.

The 404 is from Dropbox and indicates that the request has not successfully reached a Dropbox API endpoint. The issue is that you're sending a PUT, but you need to use POST to hit /2/files/upload. Please update your code to use POST and try again.

Apologies for the trouble with the spam filter. I've recovered your post and will take a look and reply there.

[Cross-linking for reference: https://stackoverflow.com/questions/79284194/how-to-download-files-from-a-public-dropbox-and-onedrive-folder ] Using the Dropbox JavaScript SDK, to list the contents of a folder using a shared link to the folder, use the filesListFolder/filesListFolderContinue functionality. Send the shared…

This should be working again now. Thanks again for the report.