Greg-DB Dropbox Community Moderator

Comments

  • The Dropbox OAuth app authorization page should only be processed in the user's system browser. Using a web view is not officially supported, so I'm afraid I can't offer help with this. That said, Android 4.4.2 itself is relatively old and I believe is itself no longer officially supported by Google, so you may want to…
  • It looks like the Dropbox API itself and the code to call it are working as expected, so I'm afraid I can't offer much more insight. It sounds like there's something in your app that is interfering with the proper execution of the call. You'll need to debug your app's code and environment further to track down the issue. 
  • [Cross-linking for reference: https://stackoverflow.com/questions/55451478/xhrhttprequest-to-dropbox-xhr-failed-loading-options ] The https://content.dropboxapi.com/2/files/upload endpoint is still the correct way to upload files (smaller than 150 MB). I just tried it, and it is working for me. If something's not working…
  • We can't offer help with Auth0 itself, but we'll be happy to help with the Dropbox side of things. An OAuth 2 access token for the Dropbox API should work the same way regardless of exactly where/how you get it (e.g., from the app's info page on Dropbox App Console, or from the actual Dropbox OAuth app authorization page),…
  • This error message indicates that the operation (e.g., uploading a file or creating a folder) couldn't be completed because there is already a folder at the specified path. The .NET SDK 'SimpleTest' examples uses a folder named "DotNetApi" in the root of the connected Dropbox account to store the test files, so this error…
  • This is a known issue on our side when attempting to download from this kind of link using the /2/sharing/get_shared_link_file endpoint. I don't have a timeline for a fix unfortunately, but I'll follow up here once I have any news.
  • @"Ben_Indy" No, unfortunately I don't have any news on this. We appreciate the feedback though! I'll send it along to the team.
  • I'm glad to hear you sorted this out already. By the way, the uploadAndFinish method returns a `FileMetadata` when it successfully runs, so you can programmatically check that return value for details on the uploaded file.
  • No, unfortunately the Dropbox API doesn't offer a way to determine which files are currently syncing, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.
  • @"tianhong" Thanks for the feedback! The documentation for the Python SDK is linked from the SDK's readme, and all of the options for the `Dropbox` class can be found on this `Dropbox` documentation page in particular. I certainly understand how that may not be very discoverable though, so we'll think about ways to make…
  • @"klm1" Thanks for the feedback! I can't make any promises, but I'll ask the team to update that page to clarify this.
  • @"tianhong" To set the 'Dropbox-API-Path-Root' header, you should instead use the provided 'Dropbox.with_path_root' method, like this: dbx = dropbox.Dropbox(TOKEN).with_path_root(dropbox.common.PathRoot.namespace_id("1990815600")) dbx.files_list_folder('')
  • The 'assets' field is documented under /2/team_log/get_events. Make sure you click through 'TeamEvent' > 'AssetLogInfo' for the full description: Zero or more content assets involved in the action. Currently these include Dropbox files and folders but in the future we might add other asset types such as Paper documents,…
  • The code from that blog post expects `file` to be a JavaScript `File` object. I'm not sure what the `event.getParam` does in your version of the code, but it appears it's not retrieving the actual `File` object, and so is instead just uploading the string representation "[object Object]" of whatever object it is returning.…
  • To download a file, you would use files_download. There's an example of using that here.
  • @"LukFromTheSky" No, unfortunately I don't have an update on either of these feature requests.
  • The error message you shared indicates an issue at the transport layer, so the particular API endpoint, Dropbox file, or async job shouldn't matter. (Those are all only used after the secure connection is negotiated.) The Dropbox API servers are currently being served with valid TLS configurations though (e.g., see the SSL…
  • The 'www.dropbox.com site' doesn't allow CORS like this. You can technically make this work using 'dl.dropboxusercontent.com' (e.g., "http://dl.dropboxusercontent.com/s/8g7fump2tnbohv2/items.json"), but please note that isn't officially supported.
  • For programmatically uploading and downloading to/from Dropbox in Python, we recommend using the official Dropbox API v2 Python SDK. There's a sample app here that shows how to upload and download files.
  • The "state" value for the Dropbox OAuth app authorization flow is: Up to 500 bytes of arbitrary data that will be passed back to your redirect URI. This parameter should be used to protect against cross-site request forgery (CSRF). See Sections 4.4.1.8 and 4.4.2.5 of the OAuth 2.0 threat model spec. Exactly what you put in…
  • Additionally, if you are a programmer willing to write code to do this yourself, one way you may be able to do this without downloading everything, is via the /2/files/save_url. If you can get Internet-accessible links for the files you want to save to Dropbox, you can use that endpoint to have Dropbox save them directly.
  • Based on your reference to "the choose module", it sounds like you're referring to using the Dropbox Chooser and saving the link to chosen file(s). The Dropbox Chooser is intended as a way for third party applciations to easily let users select files from their accounts, returning the links for those files to the app. What…
  • For client-side applications in particlar, such as in browser JavaScript, using the "token" a.k.a. "implicit" Dropbox OAuth app authorization flow is the expected and reccomended technique. That is supported by the official Dropbox JavaScript SDK. You can see it getting set in the SDK's code here if you're interested, and…
  • Yes, if you want to list and monitor the file changes for all of the members of your Business team, there are two ways you may go about it: * Using /2/team_log/get_events[/continue] with a Dropbox Business API app with "team auditing" access: This allows you to list and then continue to monitor file change events for all…
  • @"chibimagic" Are you referring to the Getting Started PDF in particular? If so, please try again now and let me know if you're still seeing this issue.
  • @"billGeb" That's correct, unfortunately you can't directly modify the shared link for a folder containing files in order to get a shared link for one of those files. (If you browse through the web page for a shared link for a folder manually, for instance, you'll see that it's more than just the file path that changes in…
  • Are the namespace IDs for the team members' home folders? By default, API calls operate using the member's home folder as the "root", but you can't retrieve the metadata for"root". So, while the folders have contents that can be listed, you can't retrieve the metadata for the folder itself. For teams using the team space…
  • Yes, for client-side apps, you should use the "implicit" a.k.a. "token" flow. This is the version of the Dropbox OAuth app authorization flow that does not require use of the app secret. The DbxWebAuth class in the official Dropbox API v2 Java SDK is only built for web apps though, and does not support the implicit…
  • I'm sorry to hear about your trouble in the support ticket. In some simple cases in the past I have been able to get the issue rectified directly, but I cannot always do so. Anyway, it looks like the support agent on your ticket was confused. I'll re-open it and redirect it to the right people.
  • Thanks! Based on the code you shared, I see that you're using the "code" flow (i.e., 'response_type=code'). For the code flow, only "https://" is allowed in the redirect URI (unless on localhost), so "myapp://" wouldn't be allowed. Instead, for client-side applications like this, you should use the "token" flow, i.e.,…