Greg-DB Dropbox Community Moderator

Thanks for the additional feedback! It is helpful.

For reference, this JavaScript SDK auth example shows how to initiate the app authorization flow: https://github.com/dropbox/dropbox-sdk-js/blob/master/examples/javascript/auth/index.html#L89 The parameter passed to getAuthenticationUrl should be where the user should be sent back to after authorizing your app. In your…

Thanks for trying that. I did find this issue on the requests GitHub that indicates this should be fixed in 2.18.1 though: https://github.com/requests/requests/issues/4160 Can you try adding the print statement in dropbox.py directly (i.e., our library, not your dbox.py) to see if it's somehow picking up a different…

No, it's not possible to retrieve the app owner's account information from an app key and secret.

API v1 and API v2 offer entirely different interfaces, so you will need to update how your app integrates with Dropbox by making changes to your app's code. To use API v2, we recommend using one of the official SDKs, if possible. We don't have an SDK for PhoneGap in particular though:…

Once API v1 is retired, any further API v1 calls will fail with a 400 error with the body: {"error": "v1_retired"} This would be translated to a native error type in the SDKs. So, if users try to access Dropbox functionality via API v1 after it is retired, that functionality will not work. The exact user experience will…

When using the OAuth 2 "token" flow, only the app key is necessary and the app secret isn't used. In the "code" flow, both the app key and secret are necessary. You can find more information on the different OAuth 2 flows in the documentation here:…

The documentation for this method can be found here: https://dropbox.github.io/dropbox-sdk-obj-c/api-docs/latest/Classes/DBFILESUserAuthRoutes.html#/c:objc(cs)DBFILESUserAuthRoutes(im)uploadData:mode:autorename:clientModified:mute:inputData: From there, the first parameter (which is unnamed in the calling code) is the…

(I was writing this in response to your new messages, but it looks like you either deleted them or there's an issue with the forum not displaying them.) The 'path/not_found' error indicates that there's nothing at the path you specified. When referencing paths in Dropbox, you should use the remote path, not the local path…

I can reproduce this with requests==2.18.0, but not requests==2.18.1. Can you double check that 2.18.1 is actually getting used, and not 2.18.0? E.g., try doing this right before the API call, like you're doing with the Dropbox library: import requests print(requests.__version__)

The ListFolderResult.entries array contains Metadata objects. These can represent files, folders, or deleted items. The entry would be a FileMetadata, FolderMetadata, or DeletedMetadata, respectively. These are all subclasses of Metadata, but size is only available on FileMetadata. So, you should do something like this:…

The Dropbox API doesn't offer this unfortunately, but I'll be sure to pass this along as feedback. (The closest thing is the file templates/properties functionality, currently in preview, but that's only available for Dropbox Business teams/apps.)

Yes, while any further API v1 calls will fail once API v1 is retired, there's no requirement for users to begin calling API v2 before that. They can begin calling API v2 at any time, and existing access tokens will still be active.

Yes, you should use files_list_folder and files_list_folder_continue to list the contents of any folder, including root. The root path is identified by the empty string "".

Can you share the full HTTP request/response for the call with the unexpected 201 response so we can investigate? Just be sure to redact the access token. (Feel free to open a ticket instead if you'd prefer to share privately: https://www.dropbox.com/developers/contact ) Thanks in advance!

This secondary issue should also be fixed now.

The SwiftyDropbox library runs API requests for these methods asynchronously. That is, when you call client.files.upload, that method will return before the API request itself completes. So, to limit how many are running at once, you need control how many times you call client.files.upload to begin with. You can't just run…

Apologies for the confusion. The curl example in the documentation and API Explorer for /2/auth/token/from_oauth1 are unfortunately incorrect. I'll let the team know to fix that. That endpoint actually uses app authentication ( https://www.dropbox.com/developers/reference/auth-types#app ), so a bearer access token isn't…

According to the documentation, we only support the "bearer" token type, so any of these should be fine.

Apologies, my reply was a little misleading. It seems CURLOPT_WRITEFUNCTION doesn't return a stream object exactly, but it's a way for you to supply a function that will be called multiple times to read data off the reply a piece at a time. In any case, this is more about using curl in PHP now, which is outside my area of…

The file data is returned in the HTTP response, so you could read from it as a stream if your HTTP client supports it. It looks like PHP curl's may effectively support this via CURLOPT_WRITEFUNCTION: http://docs.php.net/function.curl-setopt

Thanks for the post! I can't speak to the intent here, but I'll send this along to the team to see if we can get that changed. I can't make any promises as to if they will do so though.

The dropbox-sdk-java repository does contain all of the source code for the API v2 Java SDK, but if you want to build from source, you'll need to following the instructions in the Building from source section of the documentation. Alternatively, you can load the library from Gradle or Maven, or download the jar files…

Note that it's not possible to change the permission on an app. You can only delete an app and create a different one, as you described. Also, every access token is tied to one and only one app. In this case, it sounds like you retrieved an access token, and then deleted the app for that access token. At that point, API…

Hi Rajul, Dropbox API access tokens aren't directly tied to API version exactly. Dropbox API access tokens are tied to OAuth version. For reference, Dropbox API v1 supports both OAuth 1 and OAuth 2. Dropbox API v2 supports only OAuth 2. We don't have documented guarantees on the exact format of either (e.g., for length),…

@"jczorkmid" I don't actually see a ticket from you. Did you use https://www.dropbox.com/developers/contact and see the green confirmation banner when you submitted it? Would you mind trying again? Thanks, and apologies for the bother.

Thanks for the post. I don't have a workaround to offer on our side unfortunately, but I'm raising this with the engineering team to see if they can change that behavior. I can't make any promises though.

I don't know offhand if anyone has used that method in with Xamarin Android. I unfortunately can't offer help with Xamarin in particular, as that's made by a third party. By the way, it looks like Xamarin publishes their own copy of the library, under "Dropbox v2 API for Xamarin" that you may want to try, if you haven't…

Hi Jeremy, the "0-SNAPSHOT" configuration would be used if you're building the SDK from source locally, but that's not strictly necessary. You should be able to install a specific version via gradle as you mentioned. In the gradle setup that you posted though, you appear to be trying to load an older version of the SDK…

@"jczorkmid" I don't have an update on this right now. This would certainly be a legitimate reason to ask for an exception though, so please feel free to do so, as above, if you haven't already. Also, to determine if the result is for a file or folder, you can check the ".tag" value in the response from…