Greg-DB Dropbox Community Moderator

@"nishu-pixofix" No, the Embedder doesn't offer a way to programmatically detect error cases like that, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

This should be working again now.

Yes, this should be working again now.

Thanks for the note. We'll look into it.

@"nishu-pixofix" There's nothing you should do to work around or mitigate the issue. The team is working on resolving it on our side.

If these are failing after an hour, that would be due to the server timeout. There isn't an option to delay or prevent that. Content-download style endpoints, such as /2/files/download, support "range requests" though. I recommend using range requests to continue downloading the rest of the data if a connection fails, and…

Thanks for the report! We'll look into it and I'll follow up here once I have an update.

Thanks for the report! We'll look into it and I'll follow up here once I have an update.

From the error message, it seems that the issue is that JSON.parse is not set to a function. The Dropbox Chooser functionality does use JSON.parse, and that should be available built-in to the web browser as that's a standard function included in web browsers. I can't offer support for mootools or any other particular…

@"roosterzappa" Thanks for sharing that!

We just made an update that should help with this. Please try again and let me know if you're still seeing this. Thanks!

@"RWMOREY" Thanks for the note. I don't know why your comment was posted in this thread, but I've now moved it to the "Searching for a specific file type" thread for you.

Thanks for the feedback!

@"idanarie" Are you using an API app registered with the "app folder" access type? There's currently a bug that results in this error when using this method with an access token for an app folder app. That's still open with engineering, but I don't have a timeline on a fix.

@"rbchapman" Thanks for following up. It sounds like what you want is to set 'include_has_explicit_shared_members: true' when calling /2/files/list_folder, so you can get 'has_explicit_shared_members' for the files in the results (and then call /2/sharing/list_file_members as needed).

The search endpoints don't support searching within a shared link, but you can use /2/files/list_folder[/continue] to list the contents (and filter client-side as needed) as you mentioned, so I suggest trying that to see if it would be sufficient for your use case. To do so, you would specify the shared link URL in the…

For reference for anyone looking for information on setting the root, please refer to the Team Files Guide.

@"AlvaroHuertas" Looking at the error and code, as Здравко said, it looks like you're trying to use a feature that your app is not actually configured for. For example, if your app is not team-linked, you wouldn't use as_admin. And for information on how to access the team space, check out the Team Files Guide.

@"Dicta" Can you please try again and let us know if you're still seeing the same issue now? Thanks!

@"raz0red" Thanks for the note. It looks like this is a different scenario, so I've separated your latest comments to a new thread. We'll look into this one scenario and I'll follow up here once I have an update on this for you.

@"cristrod817" Здравко is correct; /2/sharing/get_shared_link_metadata is for getting information about an existing shared link that you would specify. It isn't a way to create or retrieve a shared link. I see you were specifying a "url" parameter value of "https://api.dropboxapi.com/2/sharing/get_file_metadata", which is…

@"mansi2821" Yes, as Здравко said, you can access subfolders just like parent folders, such as by using the 'recursive=true' option on /2/files/list_folder. I also recommend reading the following guides for more information: * https://developers.dropbox.com/dbx-file-access-guide *…

Thanks for following up and sharing your code. I'm glad to hear you got this sorted out. To confirm, the refresh token is not the value returned by www.dropbox.com/oauth2/authorize... itself. Using www.dropbox.com/oauth2/authorize with 'response_type=code' gives an 'authorization code' (sometimes also called 'access…

A 'missing_scope' error indicates that while the app may have that scope enabled, 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. That…

This should be working again now.

Apologies for the inconvenience. There was an issue with the deployment. We're working on it.

@"Esikhoob" As it is best not to leak your app secret to users, you can instead use the "PKCE" app authorization flow with the JavaScript SDK itself. The PKCE flow is intended for client-side applications and does not require the use of the app secret. You can find an example of using it with the JavaScript SDK here.

While the option for creating 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 changes, we will of course announce that ahead of time.) That being the case, you can continue using existing long-lived access token(s) without…

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

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