Greg-DB Dropbox Community Moderator

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

@"Edlo11" You seem to be missing some of the relevant code in your fixed version. Make sure you're following the instructions as currently documented. Please update your code accordingly, and make sure you're using the latest version of the SDK, and let me know if that's still not working. Thanks!

I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with: * the name and version number of the platform and SDK/library you are using, if any * the steps to reproduce the issue, including relevant code snippet(s), but don't include your access token *…

I'll pass this request along (though we'd also run in to the same issues with Cocoapods/Carthage anyway). It looks like there are some workarounds available in the Carthage issue while they work to resolve this properly, so you may want to use one of those to get running for now. (Or, likewise use Cocoapods 1.10, which…

@"IanHarker" This issue is still open with engineering, but I don't have an update to share yet.

No, unfortunately the only officially supported installation methods for the Dropbox API v2 Objective-C SDK use Cocoapods or Carthage, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

Thanks for following up. It looks like this is due to that Carthage issue. We can't officially offer support for Carthage itself as that's not made by Dropbox though, so I'll have to defer to the information in the Carthage issue regarding this. It looks like that's currently still open. For reference though, one way to…

I recommend reading the "Detecting Changes Guide" here: https://www.dropbox.com/lp/developers/reference/detecting-changes-guide That covers the options for efficiently detecting and listing just the changes that have occurred since you last checked, e.g., using the "cursor" functionality on /2/files/list_folder[/continue].…

No, unfortunately searchV2 doesn't offer a way to include file properties in the results like this, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. There is a propertiesSearch method, if that helps for your use case, but note that only allows you to directly…

[Cross-linking for reference: https://stackoverflow.com/questions/64454739/using-server-side-ss2-x-to-upload-files-to-dropbox-body-encoding-issue ] I can't offer help with the NetSuite side of things, as that's not made by Dropbox, but for reference, the /2/files/upload Dropbox API endpoint is a "content-upload" style…

@"dhyanP" It sounds like the original poster here did get this working by iterating through the different result pages as needed and indicated by the 'has_more' value. Please see my earlier comment for more information. Is that not working for you?

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 For example, to access Dropbox file content directly, you…

This "No scope requested can be granted for this app" error message indicates that none of the "scopes" being requested during the authorization flow are registered for the app. When using a scoped app, the developer needs to enable all of the scopes that the app will need before initiating the authorization flow with…

This error message indicates that your API app has the "app folder" access type, but you're supplying the "Dropbox-API-Path-Root" header. For example, in the Dropbox API v2 JavaScript SDK, you might be setting that via the pathRoot option on the Dropbox object. Apps with the app folder access type are restricted to their…

@"sosnos" We recommend using the latest version of the official Dropbox SDK. You can find the official API v2 Dropbox JavaScript SDK here, including the official documentation and examples. That does contain the 'getAuthenticationUrl' method, documented here. You can find an example of using that here.

Thanks for the following up with this additional information. An 'invalid_root' error like this means: The root namespace id in Dropbox-API-Path-Root header is not valid. The value of this error is user's latest root info. That is, you're sending the wrong value up in withPathRoot. Note that a user's root namespace ID can…

Thanks for the additional information. If you use the official Dropbox API v2 Java SDK as provided, it should automatically send the app authorization flow through the system browser, not a webview. It sounds like you're still using a webview in this case though, even with the SDK. Please note that, regardless of system…

Thanks for the post. I've sent this along as a request for a way to get a reference to the window. I can't promise if or when that might be implemented though. As for the potential bug, I'm not sure if I follow the scenario exactly. Can you elaborate and provide some mored detailed steps for reproducing it? Perhaps you can…

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

In the case where you're using the official Dropbox API v2 Java SDK on an emulator without Google API support, can you elaborate on where you're processing the app authorization flow? If the official Dropbox Android app itself isn't installed, it should be processed through the system browser. In that case, can you also…

We're happy to help however we can, but we'd need some more information about exactly what isn't working as expected when your app is calling the API. It sounds like you're saying that the issue occurs when attempting to download a file, so you're probably referring to calling /2/files/download (either directly or via a…

@"petergoes" Thanks for the feedback!

We can't offer support for third party tools themselves, such as "Iperus", but we're happy to help on the Dropbox side of things. First, note that Dropbox supports uploading files up to 350 GB in size via the API, which would be done via upload sessions. If a single file is larger than 350 GB, you won't be able to upload…

Unfortunately, app folders are incompatible with shared folders, team folders, and team spaces, meaning you can't share an app folder (except as a link), put a shared folder or team folder inside an app folder, or put an app folder in a shared folder, team folder, or team space. Instead, if you need to use the API with…

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 The API itself is meant for custom integrations that the…

Can you print out the response body itself? (The output here is just the headers.) The body should contain a more useful error.

@"mjottii" I can't speak to what other third parties may have implemented, but on the Dropbox side there are a few updates (though nothing specific to WordPress). Dropbox now offers an App Center to list some third party integrations: https://www.dropbox.com/apps Dropbox also now offers the Dropbox Embedder, which can be…

It looks like these issues are due to incompatibilies with Xcode 12 in both Cocoapods and Carthage. For Cocoapods, please refer to this issue: https://github.com/CocoaPods/CocoaPods/issues/9902 For Carthage, please refer to this issue: https://github.com/Carthage/Carthage/issues/3019

The Dropbox API doesn't offer a way to retrieve more detailed error information. It returns the error in the response body, and this particular error just indicates that the supplied value couldn't be parsed as valid JSON. It doesn't offer a way to get more specific information about where the parsing failed within the…

Thanks for the report! We'll look into this to see what the issue may be. To make sure we reproduce the same problem you're seeing though, can you share the relevant error messages you're getting? Thanks in advance!