Greg-DB Dropbox Community Moderator

1. I'm not sure I follow. Exactly what functions are called and when is controlled by your app. You may want to step through with a debugger to see what it is doing and how to correct it. 2. You don't have to upload the same amount of data with each call. For example, when you only have less than 1 MB left to upload, you…

It sounds like "y4yp61aez2fn8" is the key for an OAuth 1 access token. There should also be a corresponding secret value for the OAuth 1 access token. With those values, you can set the access token using the updateAccessToken method I mentioned ealier. I don't have any pre-written code for this to share though, as this is…

This is working properly for me. 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 of the platform and SDK/library you are using - the steps to reproduce the issue - the full text of any error or output - the relevant…

Unfortunately the Dropbox API just happens to not have the particular functionality you're looking for. I've sent this along as feedback, but I can't promise if or when any of this functionality would be implemented.

2. You can use getSharedLinkMetadata to get the metadata, but that also requires user auth, like getSharedLinkFile. The API unfortunately doesn't offer a way enumerate the contents of a folder via a shared link for the folder.

The Dropbox API doesn't support If-Modified-Since/Last-Modifed header functionality. Instead, to check if a file has changed, you can store/check the 'rev' value in the file's metadata. For example, you can call /2/files/get_metadata and store the returned 'rev' value. When you call back later, if the 'rev' value has…

1. The Dropbox API doesn't support creating a shared link for the root path, but I'll be sure to pass this along as a feature request. (In the case of an app folder app, the app folder itself is "root".) 2. Yes, the getSharedLinkFile does require user auth, so it sounds like that won't be a good solution for you.…

[Cross-linking for reference: https://stackoverflow.com/questions/43569364/dropbox-url-masking ] Dropbox doesn't offer a way to do this, but I'll be sure to pass this along as a feature request.

The share method you're using returns a dict, so you can access the fields like: print(client.share(path)['url']) That uses API v1 though, which is deprecated. You should switch to using API v2. Using API v2, creating a shared linked is accomplished using the sharing_create_shared_link_with_settings method, which returns a…

No, you don't need to also call /upload if you're using upload sessions. You specify the path where you want to upload the file when you call /2/files/upload_session/finish. If you want to upload 1 MB at a time, you would just supply 1 MB of data to each request to /2/files/upload_session/start,…

This depends on how you've set up your version control, but generally you would put your entire project folder in version control, so that anything in that folder is covered. (I.e., both the .xcproject and the .xcworkspace files would be.) Of course, how you set up your version control repo is up to you, but I would…

1. The Dropbox API doesn't allow an app with the app folder permission to create a shared link for its own app folder. Instead, you could make a subfolder, e.g., "/Recordings" (or whatever you'd like), and then get a shared link for that folder. 2. You can download the file from a shared link using the getSharedLinkFile…

Thanks! I actually tested on 44.2.4 though, so can you try upgrading and letting me know if that helps? Also, I'm not sure I understand what you mean when you say your "app is simply not handling value". Can you elaborate? Thanks in advance!

If you want to download a file from Dropbox using the API v2 JavaScript SDK, you should use the filesDownload method: https://dropbox.github.io/dropbox-sdk-js/Dropbox.html#filesDownload__anchor There's an example of using sharingGetSharedLinkFile, which works similarly to filesDownload, here:…

That error indicates that the "token" a.k.a. "implicit" grant is disabled for that app. You can re-enable it using the "Allow implicit grant" option on the app's page on the App Console: https://www.dropbox.com/developers/apps

The term "client ID" is just another name for "app key". You can get the app key for your app from the app's page on the App Console: https://www.dropbox.com/developers/apps If that's not working for you, please share the problematic code and the error you're getting.

Un error WriteConflictError.file como este indica que la subida falló porque ya hay un archivo en la ruta donde está intentando cargar el nuevo archivo. Puede utilizar una ruta de acceso diferente, eliminar el archivo existente o utilizar un modo de escritura diferente. Puede configurar un modo en su CommitInfo para…

Are you sure you're not getting an error message? I would definitely expect some exception if the app crashed. Perhaps your log is set to a filter that isn't showing the message? If not, can you share a sample project that reproduce the issue so we can investigate?

You can post a Dropbox shared link for the project: https://www.dropbox.com/help/167 If you'd prefer to share privately, you can open an API ticket here instead: https://www.dropbox.com/developers/contact

Thanks for following up. The code I shared worked properly for me, so we'll have to look into this further. Can you let me know: - the version number of the Chooser SDK you have - the version number of the official Dropbox iOS app you have installed

This is open with the team, but I don't have an update on it yet. I'll follow up here once I do.

There are some complications around background sessions. You can find more information about that here: https://github.com/dropbox/dropbox-sdk-obj-c#note-about-background-sessions

Ok, I determined what the issue is here. Whether or not the assert occurred depended on the ENABLE_NS_ASSERTIONS build setting. By default, that build setting varies depending on which scheme you're building for. (It's Debug:Yes, Release:No.) When using Cocoapods (as I often do when testing things) the scheme used for the…

Your code looks fine, and it's working for me (as long as I remove the TextView code). When you say "the app just stops" though, does the app actually stop running, or is it hung on something? If it's the former, I would certainly expect some sort of error or output. If it's the latter though, perhaps the network call…

Yes, please do share that modified version of SimpleTest so we can reproduce this and look into it. Thanks in advance!

You appear to be constructing your own DBChooserResult object instead of using the one(s) in the results array returned by Dropbox. You should instead do something like this: DBChooser.default().open(for: DBChooserLinkTypeDirect, from: self, completion: { results in if ((results?.count) != 0) { for case let result as…

That code seems to work for me. Can you elaborate on how you're using it and how you're checking that it never returns? Alternatively, would await work in your scenario? await DropboxOAuth2Helper.ProcessCodeFlowAsync(authorizationCode, appKey, appSecret);

The plan-based limit shouldn't come in to play here. Any limiting like that would return explicit errors, not slowdowns. If you'd like use to investigate this specifically, please open a ticket from the affected account: https://www.dropbox.com/developers/contact Thanks!

Interesting. In that case I'll dig into it further now that I can reproduce it. Thanks!

This project does not fire the assert for me. It does print: yah 0 yah 0 What's different in this project? Did you change a project setting or is it something in the code?