Greg-DB Dropbox Community Moderator

I don't believe that's called out specifically in the documentation, but that information from the error message is correct. (It's also shown in the curl examples.)

We've corrected the ordering in v8.3.1 so that developers don't need to update their code when upgrading from 8.2. (If you have already done so though, you will need to revert that change, or, preferably, switch to using named parameters. Apologies for again for the bother.)

This should be working again now. Apologies for the interruption!

The latest version of the SDK is v3.3.3. If you're using 1.1.1, you will see the discrepancies with the current documentation you mentioned. We recommend updating to the latest version. For Cocoapods, you'lld need to run `pod update`. If your Podfile is set to require 1.1.1 (or some other version) specifically, remove the…

Thanks for the report! It looks like there may be a service disruption on our side for webhooks right now. We're looking into it.

@"maki1986" The Dropbox Chooser allows your app to easily request files from users. Once the user selects a file, the Chooser returns a link for that file to your app. If your app used the "direct" link option, it can then directly access that file content, but exactly how you manage that is up to your app.

@"Steve L.26" The batchUploadFiles method isn't a direct API call, but rather a convenience method built to wrap the various upload sessions calls, so it doesn't directly expose the API errors. It instead exposes different error cases via the different values in the overall response block that you mentioned. If you want…

The equivalent of that in the API v2 Objective-C SDK would be getTemporaryLink: https://dropbox.github.io/dropbox-sdk-obj-c/api-docs/latest/Classes/DBFILESUserAuthRoutes.html#/c:objc(cs)DBFILESUserAuthRoutes(im)getTemporaryLink:

What information exactly are you looking for? You can find the documentation for the HTTP interface here: https://www.dropbox.com/developers/documentation/http/documentation The specification for the API can be found here: https://github.com/dropbox/dropbox-api-spec

@"mrschulz" I'm sorry to hear this caught you unaware. We notified developers by email, but it sounds like those emails unfortunately did not make it to you. If you need more time to migrate your app to API v2, we can offer an extension for access to API v1. To request that, please open an API ticket with the relevant app…

@"ShiminCai" We don't have a migration guide for moving between these SDKs in particular. I recommend just reading through the readme for SwiftyDropbox, which covers the different kinds of calls, to see how each piece should be implemented.

@"philipkd" The version of the API used to create files/folders does not somehow taint those files/folders. Are you sure these users are looking in the right folders, and the right accounts? If you can reproduce any API calls yielding unexpected results, please share the details and we'll be happy to look into it.

The 'id' can be used with various endpoints, in place of the file path. In many cases, you can just pass in the 'id' string in the 'path' parameter. For example, you can pass the 'id' as the 'path' value when calling /2/files/get_metadata. That's an easy way to check if a file or folder exists. The…

@"Clifton L." Are you still seeing "Logbook.db" returned now when searching "Logbook.pilotpro"?

@"suzuka" If you have the metadata for a file or folder, e.g., as returned by /2/files/get_metadata, that will include a path_lower, like: "/homework/math/prime_numbers.txt" You can parse the path to get the parent folder, e.g., in this example: "/homework/math" You can then use /2/files/get_metadata again with that path…

@"correotorrent" It sounds like you're getting this error because we retired API v1 recently. I would need to see the actual error response you're getting to confirm that though. For reference, if that is the issue, as announced last year, API v1 has been retired. You can find more information in the blog post here:…

When making an API call like this, the 'path' value you supply should be the file path and name where you want to upload the file. In your case, you're just supplying "/Apps", so that's what the file will be saved as. You should instead supply something like "/myfolder/originalfilename.sav". That is, include the name and…

[Cross-linking for reference: https://stackoverflow.com/questions/46619550/uploadwritefailedreason-writeerrordisallowed-name-none ]

@"brian q." The /2/files/upload_session/finish endpoint should already be returning full FileMetadata objects, per the documentation. That includes both the path_lower and id for the uploaded file. Is that not what you're getting? If not, please share a full sample request/response so we can take a look. (Just redact the…

I'm glad to hear you sorted this out already. Yes, you can directly access those fields like that, no regex necessary. For anyone else looking for this, here's that sample cleaned up: import dropbox dbx = dropbox.Dropbox("<ACCESS_TOKEN>") myDir = dbx.files_list_folder("") for item in myDir.entries: if isinstance(item,…

@"SnowJeb" The example should work. Can you share the specific errors you're getting so we can help? Thanks in advance! 

@"Singingmaya" The forum shows a date in the upper right of each comment, and there's a more specific timestamp shown if you hover over it: Hope this helps!

1) No, the Chooser/Saver domains specify which domains can use your app key for the Chooser/Saver. That does not affect the resulting links. 2) That sounds like an issue with the web site. Please open a ticket here for help with that: https://www.dropbox.com/support And thanks for the feedback!

Thanks! That looks like a bug in SwiftyDropbox v4.2.0 when using Xcode 8. We'll look into it. In the meantime, you can use v4.1.2, by specifying it in your Podfile like: pod 'SwiftyDropbox' => '4.1.2' Then, do a `pod update`.

Can you share some code to reproduce the issue? I'm not sure off hand what the issue may be, but we'll be happy to look into it. Thanks in advance!

Yes, I would expect the value should be at least the size of one chunk (e.g., if only one chunk succeeded). What chunk size are you using? We generally recommend something much larger than 15, e.g., 8 MB (8388608 bytes).

This should be resolved now.

It looks like you're getting an old version of SwiftyDropbox (3.3.1) and consequently an old version of Alamofire (3.5.1). You should be getting 4.2.0 and 4.4.0, respectively. It's not clear why you're getting the old versions though. Can you try the following? pod cache clean --all pod repo update pod update

The correct_offset value indicates what byte index in the upload the Dropbox API servers expect next. This may not always match what your app expects, e.g., in cases where the app and server were unable to communicate. For example, if a previous request was received, but the response never made it to the app. When this…

Yes, the shared links returned by the Chooser are the same kind of shared link as used by the general shared link feature in Dropbox: https://www.dropbox.com/help/files-folders/view-only-access That allows anyone with the link to access the shared content. Users can always revoke these shared links from the web site:…