Greg-DB Dropbox Community Moderator

Comments

  • @"waltertross" Thanks for the note!
  • Thanks for following up. I'm glad to hear you already sorted this out. Yes, the Dropbox API OAuth 2 authorization codes can only be used once each. 
  • Thanks for following up. We don't have a public roadmap for features. This forum thread serves as the feature request and I've sent it along to the team.
  • Dropbox doesn't currently offer a way to embed or iframe Paper docs like this, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 
  • @"rajshree1996" No, unfortunately the Dropbox API doesn't currently support creating folders using paths relative to existing folder IDs, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. It does support creating new folders relative to namespace IDs though, like:…
  • [Cross-linking for reference: https://stackoverflow.com/questions/58112294/download-dropbox-images-to-netlify-build-folder ] It looks like you already worked out the solution on StackOverflow.
  • Thanks for the report. If/when a webhook URI is automatically disabled, we do send an email notifying you of that. Please make sure that the email address on the account that owns the app is up to date and can receive email from the official Dropbox email domains. It sounds like this the webhooks functionality is working…
  • If you're using the Dropbox Java SDK with an app with the "team member file access" permission and want to download files via the team member file access feature, you should first make a DbxTeamClientV2 with the team's access token. Then, you can call DbxTeamClientV2.asAdmin or DbxTeamClientV2.asMember, depending on your…
  • Based on the code you shared, it looks like you're using this third party dropbox-v2-api library. Since that's made by a third party, we can't provide support for it. You may wish to refer to the documentation for it or open an issue there for help using it.
  • @"namiqismayil" The Dropbox Chooser is only designed and supported for running in standard browser environments, so unfortunately it won't work in Outlook Add-ins like this. I'll pass this along as a feature request for support for this, but I can't promise if or when that might be implemented. 
  • It looks like there are a few issues here: * Based on "mDBApi.putFile", it looks like you're using an old and now retired Dropbox API (v1) and SDK. You should instead use Dropbox API v2. For accessing Dropbox API v2 from Android, we recommend using the official Dropbox API v2 Java SDK. There's an example Android app using…
  • I'm not sure I follow your question. For reference: * The /2/sharing/create_shared_link_with_settings endpoint can be used to create a shared link for any type of file. The shared link page by default will show a preview of the file if possible. E.g., it can display a preview of the relevant text, image, PDF, etc.,…
  • The shared link expiration functionality is only available to Dropbox Professional and Business accounts. Attempting to set an expiration from other account types will fail like that.
  • There are a few different options that you may want to try: * You can use /2/sharing/create_shared_link_with_settings to create a shared link for any file, and set an expiration (if the account is on a Professional or Business plan). You can also modify these links for different behaviors. * You can…
  • @"blurymind" Thanks for sharing this! Please note though that the Saver only officially supports HTTP and HTTPS URIs, so while data URIs like this may happen to work, I don't recommend relying on that. It may not work consistently, or may break without notice. Also, yes, the Chooser and Saver do need to run on a hosted…
  • 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 Dropbox API supports two different OAuth 2 authorization flows: "code" and "token". The code flow requires the use of an authorization code. The token flow does not. The token flow is generally meant for client-side applications though, and does require a redirect URI, where the access token is return on the URL…
  • @"blurymind" No, the Dropbox Saver still doesn't support saving blobs, or some other local alternative. I'll add your vote to the feature request, but I can't promise if or when that might be implemented. The Dropbox Saver only supports saving from Internet-accessible URLs. If you want to use the Saver to save a text file,…
  • @"waltertross" We don't have a public feature request tracker. This forum thread itself serves as reference to this request, and I'll follow up here if/when I have any update on this. I don't have any news to report on this feature request right now. 
  • Based on your mention of using this on Android, I take it you're running this with Xamarin. Is that correct? The .NET SDK isn't officially supported for Xamarin, 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 thread with some information on this issue…
  • While it is possible to do, this isn't recommended for a variety of reasons: 1) Security: Client-side applications can't keep secrets, meaning that any access token stored in a distributed app could be extracted directly, or sniffed in transit. That means that a malicious user could get the access token, and use it to…
  • I'm not entirely sure I understand your last message. For reference, the API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. To do so, you wouldn't include your own access token in the app, and would instead send each user through the OAuth app…
  • You shouldn't ever handle the user's Dropbox username and password directly. Instead, you send the user through the OAuth app authorization flow, where they use the Dropbox web site to choose whether or not to authorize your app. If they authorize your app, your app will then receive an access token your can store and…
  • Thanks for the detailed post. No, I'm afraid I can't offer a way to use that undocumented functionality. Any undocumented functionality like this may be in flux and subject to break or dissapear without notice. I'll pass this along as a feature request to officially document and support this (in addition to blob support in…
  • No, unfortunately the Dropbox API doesn't expose these additional fields, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. If you want to retrieve this information, you'd need to download the file and parse out that data from the file.
  • Thanks for following up. I'm glad to hear you got this working as desired. Yes, that's correct, there's no need to apply an additional encoding. Dropbox will accept whatever data you upload exactly as you upload it. So, if you want to upload an image that can be viewed later, you should just upload the unmodified raw data.
  • @"ManikandanIndia" I'm afraid I can't offer much help with this since this is more about managing dependencies in Visual Studio/NuGet/.NET as opposed to using the Dropbox API itself, but maybe @"Nicodk" can offer some advice. Otherwise, there are some posts with detials and fixes for similar errors that may be useful: *…
  • To retrieve the additional media information for a media file like this via API v2, call /2/files/get_metadata with include_media_info:true. If the media information is available for the file, it will be included in the FileMetadata.media_info in the response.
  • It sounds like you're using a third party library for connecting to Dropbox. Since that's made by a third party, we can't provide any support for the library itself. If you're having any trouble with the library, I recommend referring to its documentation or contacting its developers. If you're having any trouble with the…
  • Thanks for clarifying! I'm sending this along as a feature request, though I can't promise if or when that might be implemented.