Greg-DB Dropbox Community Moderator

Comments

  • I'm afraid I don't have a great solution for you, as OAuth 2 redirect URIs for the Dropbox API are required to be pre-registered exactly. I'll be sure to pass this along as feedback though. One thing you may be able to do instead is to use one static redirect URI but encode the necessary information in the 'state'…
  • That depends on what you have specified in your Cartfile. If you have a specific version number or range set, you may need to update that before you call update. But yes, once you have your Cartfile configured as desired, just run "carthage update --platform iOS" to update. You can then check the console output or…
  • You can use listSharedLinks to list existing links. In this case, it sounds like you'd want to pass in the path of the folder as "path", and use "directOnly=true" to get only the link you're interested in.
  • Thanks for the additional information. Can you share the request itself though? That should help show what the issue is. And yes, if you just need an access token for your own account on your own app, you can use that 'Generate' button to get one. The page will show it to you, and you should then copy it from the page, and…
  • That's correct, API v1 is deprecated and will be retired in a few months: https://blogs.dropbox.com/developers/2016/06/api-v1-deprecated/ The 2.0.6 and 3.0.0 releases of the Java SDK both contain API v2 functionality, but also contain API v1 functionality, for backwards compatibility. You should check that you're not using…
  • It sounds like you've already applied for production, so your app will be reviewed once you have 50 linked users: https://www.dropbox.com/developers/reference/developer-guide#production-approval If it already has 50 linked users and don't receive a response soon, feel free to open a ticket so we can check on it for you:…
  • Regarding the 413 error, can you share the HTTP request being sent? (Just be sure to redact the access token.) A 413 error should indicate that the request payload was too large, so we should first determine what you're sending. Also, when you refer to your OAuth 2 "key", do you mean your OAuth 2 access token? The access…
  • If I understand your scenario correctly, the actual behavior here is correct and expected. You retrieved the cursor after those changes were made, so /2/files/list_folder/continue won't/shouldn't tell you about them when you call with that cursor. (It would tell you about changes that occurred after you retrieved that…
  • If you're using the API v2 Objective-C SDK, you can use the shareFolder method to share a folder, and then the addFolderMember method to invite other users.
  • 1. If your app is registered for the "app folder" permission, it cannot access anything outside of its own app folder. If you need your app to access items outside an app folder, you'll need to register another app for the "full Dropbox" permission instead. Note that apps registered for the full Dropbox permission do not…
  • Based on your code, it looks like you're using this third party DropboxRestAPI library. Is that correct? If so, unfortunately I'm afraid I can't be of much help, as we can't support third party libraries themselves. Also, it appears that one uses API v1, which is deprecated. You should migrate to API v2. We have an…
  • No, app folders are incompatible with shared folders. That is, app folders can't contain shared folders, be contained in shared folders, or themselves be shared as shared folders. If you need your app to interact with shared folders, you'll need to use full Dropbox access. If you do use shared folder (e.g., via a…
  • Thanks for the feedback! Unfortunately I'm afraid I don't have a good non-API v1 solution to offer. I'm sending these requests along to the team.
  • @"incode4it" That value looks right. Can you share your code, or the full/raw request and response? Just be sure to redact the access token itself. By the way, I redacted your access token from your post, but for the sake of security, you should disable that access token since you posted it publicly. You can do so by…
  • Unfortunately, the Dropbox API doesn't offer a way to do that, but I'll be sure to pass this along as a feature request.
  • 1. No, it's not possible to specify a custom limit like this, but I'll be sure to pass this along as a feature request. 2. No, the Dropbox API doesn't offer server-side filtering like that. You'll need to filter client-side. We'll consider it a feature request as well.
  • Thanks jwpegram! That's correct, the listFolderContinue response will be structured similarly to listFolder, and will only contain further/new entries, not the same entries already returned by listFolder. Also, each listFolder/Continue response generally won't be more than around 2,000 items, but that can vary, so don't…
  • Thanks for following up, and apologies for any confusion. It sounds like you are getting DeletedMetadata returned, and those are expected fields for a DeletedMetadata object. You can find the documentation for it if you click to expand "DeletedMetadata" in the HTTP documentation, e.g., under /2/files/get_metadata. Dropbox…
  • It looks like you're using a third party library for connecting to the Dropbox API, so I'm afraid I can't offer much insight on that. We can't support third party libraries themselves as we didn't make them. That said, when uploading to the Dropbox API, the file type doesn't make a difference really. The Dropbox API will…
  • Are you sending the entire 750 MB in a single UploadSessionStart call? We recommend not sending more than 150 MB in any single call (and sending less than that is probably better in fact). I can't say for sure what this issue is based on this stack, but sending 750 MB at once would certainly be an issue. The documentation…
  • Thanks! That's helpful, and it's what I expected. In this case, the best solution would be to configure your localhost server to respond to that GET request with a simple HTML success page of your liking.
  • The OAuth 1 and OAuth 2 flows do work a bit differently. With the OAuth 2 "code" flow, which it sounds like you're using, the user is sent to the specified redirect URI after they authorize your app. That's how the app receives the authorization code. Often, this is just an Internet-hosted web page, so the user sees…
  • @"wishfuluser" Unfortunately I'm afraid I don't have anyone in particular I can direct you to.
  • The account creation option was actually removed in favor of the app link in order to comply with Apple's App Store policies, unfortunately. For reference though, this behavior is controlled via the 'disable_signup' parameter on the /authorize page. It defaults to 'false', but is set to 'true' in the iOS SDKs in particular…
  • Hi, it sounds like you're using the official API v2 Objective-C SDK. Is that correct? If so, the SDK handles the access token retrieval and storage for you, regardless of which flow exactly was used (e.g., via app or web). If you're using that SDK, you should just implement the authorization flow as documented here. That…
  • No, the upload endpoints don't support file IDs unfortunately, but I'll be sure to pass this along as a feature request.
  • The API unfortunately doesn't offer any way to upload or edit Paper documents yet, but I'll be sure to pass this along as a feature request.
  • Thanks for following up. This is an issue on our side, but I don't have a timeline for a fix right now. It appears to be due to the app folder name set for your app. You may be able to work around this issue by changing the app folder name setting for your app on the App Console: https://www.dropbox.com/developers/apps…
  • Yes, in the official Dropbox API v2 Java SDK it's available as FileMetadata.contentHash.
  • You can access the results ****** ID like this: switch result { case .none: print("Empty result") case .some(let unwrappedResult): switch unwrappedResult { case .asyncJobId(let asyncJobId): print(asyncJobId) case .complete: print("****** is complete") } } Hope this helps!