Greg-DB Dropbox Community Moderator

On the Dropbox side, there's no special documentation since this would just utilize the normal OAuth flow, documented here: https://www.dropbox.com/developers/core/docs#oa2-authorize https://www.dropbox.com/developers/reference/oauthguide I don't know if Apple offers any guidance or documentation on the Apple TV side of…

Thanks for the feedback! At this point, we're recommending developers use the flow I described earlier, especially since this is already possible with the existing API. It's also the same as how connecting providers is already done on the existing Apple TV product:

Thanks for the information! Do you have any documentation for the input method using an iOS device you can link to? 

I don't have any updates on this, either internally or externally. We'd love to hear if anyone has experimented with the flow I mentioned in my last reply though, as we imagine that'd be a much better experience for the user than trying to enter all of their credentials on the TV.

Thanks for all of the information and screenshots guys, that's very helpful. I'll bring this up with the team internally. One thing that may work with the existing infrastructure though would be how Apple TV apps of the current generation work for connecting external accounts. That is, the Apple TV app gives the user a…

Thanks for posting about this. Can you elaborate on what you mean when you say "the UI does not meet the tvOS requirements"? Can you link to any relevant documentation? Once we have a better understanding of the capabilities available, we'll be happy to investigate to see if/what solution we might be able to offer.

You should not use the rev to track changes to files across moves/renames, and in fact the rev value is always expected to change when a file is moved or renamed. Be careful when comparing rev values by eye though, as subsequent values may differ only very subtly, e.g., by changing a single character slightly. Anyway, API…

This maintenance is complete and normal Dropbox service has resumed.

That's correct, these endpoints will be available in the SDKs in the next releases.

This is now available in API v2: https://www.dropbox.com/developers/documentation/http/documentation#files-copy_reference-get https://www.dropbox.com/developers/documentation/http/documentation#files-copy_reference-save

This isn't currently implemented in API v2, but I'll be sure to pass this along as a feature request.

Links using http:// on dl.dropboxusercontent.com should be working again now. For the sake of security though, we still highly recommend using only https:// links.

Thanks for the report. The servers for dl.dropboxusercontent.com are not currently listening on port 80, meaning that http:// requests won't work. We're looking into whether or not we can re-enable that, but for the sake of security we highly recommend switching to using https:// only. In the Android Core SDK media…

Thanks Jonas! That's helpful, and I'm able to reproduce the issue now. The issue is that the "-[DBDemo.ViewController handleDidLinkNotification:]: unrecognized selector sent to instance ..." error occurs inside openURL, causing the openURL operation to itself report the "unsupported URL" error. The actual issue is that in…

Thanks for clarifying. So it sounds like the login/app authorization flow doesn't work when you get the "unsupported URL" error? It looks like you're using the iOS Core SDK in a Swift project. Can you share the relevant code snippets from your app as text so we can try to reproduce this and track down the issue? (Or if you…

Hi Jonas, can you elaborate on what functionality, if any, isn't working as expected? The "-canOpenURL: failed for URL: "dbapi-2://1/connect" - error: "(null)" message is expected and safe to ignore in the simulator, where the official Dropbox app isn't installed, as the SDK will fall back to the built in flow.

There's no update on the issue of getting the ID for a deleted folder. I'll follow up on your GitHub issue regarding getting metadata from getMetadata for deleted items.

No update on this right now.

Hi Eric, no, there's no update on this right now. In the future though, please do not post on multiple threads for the same issue.

The sample app included with the SDK is a working, standalone app that you can run by itself, unrelated to your own app. Anyway, Dropbox itself doesn't really control when onActivityResult gets called, since that's just part of the Android app lifecycle. I still suspect this is due to how Cordova works, so you may need to…

Thanks! Does the sample app in the SDK work for you though? That might be a good indicator of whether or not Cordova is relevant to the issue.

Can you share: - the version number of the Android Chooser SDK you're using - the relevant code snippets - whether or not the example app included with the SDK works for you? Thanks in advance! 

Also, for reference, if you're using the iOS Core SDK, that corresponds to this method: - (void)moveFrom:(NSString*)fromPath toPath:(NSString *)toPath;

Unfortunately no, using the Chooser in a Cordova app isn't officially supported, but I'll be sure to pass this along as feedback. 

To elaborate a bit, Steve is referring to the links returned by createTemporaryDirectUrl, which always expire after four hours. The links returned by createShareableUrl do not expire by default. Users can set expirations on these links manually, using the Dropbox web site, but this isn't currently available via the API.…

The URL dropbox.com/home corresponds to the root of a Dropbox account. To list the root of a Dropbox account using Dropbox API v2, you would use the /files/list_folder and /files/list_folder/continue endpoints. The path parameter to represent root should be the empty string: ". For example, calling /files/list_folder with…

By the way, for the sake of security, you should disable that access token now that you've shared it publicly. You can do so by revoking access to the app entirely, if the access token is for your account, here: https://www.dropbox.com/account/security Or, you can disable just this access token using the…

The error message is: "'inStream' has bad type; expecting resource, got boolean'". That's indicating that $inStream, the third parameter to uploadFileChunked, per the documentation, which is supposed to be a resource, was actually a boolean. In your code, you're giving the variable $f for that parameter, so you should…

Unfortunately I don't believe we have sample code for that in particular. The documentation I linked to describes how to use it though, so give it a try and let us know if you run into any issues.

For large files like this, you should use chunked uploading instead: https://dropbox.github.io/dropbox-sdk-php/api-docs/v1.1.x/class-Dropbox.Client.html#_chunkedUploadStart